 Messages in this thread SubjectABI coupling to hypervisors via
CONFIG_PARAVIRT  * Linus Torvalds <> wrote:  > > Sure, that's
clean, From that perspective the apic is a bunch of > >
registers backed by a state machine or something. > I think you
could do much worse than just decide to pick the > IO-APIC/lapic
as your "virtual interrupt controller model". So I do > *not*
think that APICRead/APICWrite are in any way horrible interfaces
> for a virtual interrupt controller. In many ways, you then
have a > tested and known interface to work with.  yes - but we
already support the raw hardware ABI, in the native kernel.
paravirt_ops is not 'just another PC sub-arch'. It is not 'just
another hardware driver'. It is not 'just another x86 CPU'.
paravirt_ops is much wider than that, it hooks everywhere and
has effect on everything!  Lets take a look at the raw numbers.
Here's a typical distro kernel vmlinux, with and without
CONFIG_PARAVIRT [with no paravirt backend  text data bss dec hex
filename 139863 49010 57672