[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] x86/altp2m: Allow setting the #VE info page for an arbitrary VCPU
On 07/31/2018 08:19 PM, Tamas K Lengyel wrote: > On Tue, Jul 31, 2018 at 5:53 AM Jan Beulich <JBeulich@xxxxxxxx> wrote: >> I'd like you to outline in the description how you mean an external >> agent to coordinate the use of this GFN with the guest (and in >> particular without in-guest agent). > > Using #VE without an in-guest agent isn't really possible so this is > really just about designating the page from dom0 instead of doing it > with the in-guest agent. Something has to be present in the guest to > handle the new interrupts coming from #VE after all. I could image a > number of ways to coordinate that dom0 agent now setting this page > with the guest, my immediate guess is that it would be done through > the vm_event guest request channel. But it could also be done through > xenstore or even ssh. That's exactly what happens - they coordinate via the guest-request vm_event. There's a #VE driver in the guest. Thanks, Razvan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |