* Daniel Arai ([email protected]) wrote:
> To elaborate a bit more, the "ROM" layer is "published" by the hypervisor.
> This layer of abstraction will let you take a VMI-compiled kernel and run
> it efficiently on any hypervisor that exports a VMI interface - even one
> that you didn't know about (or didn't exist) when you compiled your kernel.
>
> If the ROM part is compiled into the code, then you have to compile in
> support for the specific hypervisor(s) you want to run on. It might be
> reasonable for this code to be in a lodable kernel module, rather than a
> device ROM per se, but you still want that kernel module to be provided by
> the hypervisor.
I don't agree. That module may know how to get interface info from a
vdso analog (just like a driver knows the hardware details of the device
it's interacting with, but the core kernel api is unaware), but placing
the binary compatibility on the kernel proper is wrong IMO.
thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
