On 23.04.21 11:50, Paolo Bonzini wrote:
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you can confirm the sender and
know thecontent is safe.
On 23/04/21 11:24, Alexander Graf wrote:
I can see how that may get interesting for other overlay pages later,
but this one in particular is just an MSR write, no? Is there any reason
we can't just use the user space MSR handling logic instead?
What's missing then is a way to pull the hcall page contents from KVM.
But even there I'm not convinced that KVM should be the reference point
for its contents. Isn't user space in an as good position to assemble it?
In theory userspace doesn't know how KVM wishes to implement the
hypercall page, especially if Xen hypercalls are enabled as well.
I'm not sure I agree with that sentiment :). User space is the one that
sets the xen compat mode. All we need to do is declare the ORing as part
of the KVM ABI. Which we effectively are doing already, because it's
part of the ABI to the guest, no?
But userspace has two plausible ways to get the page contents:
1) add a ioctl to write the hypercall page contents to an arbitrary
userspace address
2) after userspace updates the memslots to add the overlay page at the
right place, use KVM_SET_MSR from userspace (which won't be filtered
because it's host initiated)
The second has the advantage of not needing any new code at all, but
it's a bit more ugly.
The more of all of that hyper-v code we can have live in user space, the
happier I am :).
Alex
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
