Re: Xenner design and kvm msr handling

[Avi Kivity <avi@redhat.com>]

Gerd Hoffmann wrote:
> On 04/20/09 15:45, Avi Kivity wrote:
>
>> Please elaborate. What hypercalls are so simple that an exit into the
>> hypervisor is not necessary?
>
> Ok, that becomes a longer story.  I try to keep it short though ...
>

Thanks, this is very helpful.

>
> xenner & pv-on-hvm
> ==================
>
> Once we have all this in qemu it is just a small step to also support 
> xenish pv-on-hvm drivers in qemu using the xenner emulation bits. 
> Hypercalls are handled by a small pic binary loaded into the hypercall 
> pages.  Loading of the binary is triggered by the msr writes 
> discussed. Size of the binary is only two pages: one hypercall entry 
> points, one code.  Communication path is the very same ioport 
> interface also used by emu, i.e. it does *not* use vmcall and thus no 
> opcode changes are needed on migration.
>
This gives a good case for exporting MSRs to userspace.

Can you explain the protocol used by this MSR?  How does the guest know 
how many pages to load?  How does the kernel know which type of page to 
put where?

Note that it would still be interesting to have the guest call the 
kernel, so it can kick the host kernel Xen netback driver directly 
instead of going through qemu (and the userspace netback + tap).

-- 
error compiling committee.c: too many arguments to function