On 09.05.19 19:25, Ankur Arora wrote:Agreed about the mixed feelings part. shared_info does feel far too
HYPERVISOR_shared_info is used for irq/evtchn communication between the
guest and the host. Abstract out the setup/reset in xenhost_t such that
nested configurations can use both xenhosts simultaneously.
I have mixed feelings about this patch. Most of the shared_info stuff we
don't need for the nested case. In the end only the event channels might
be interesting, but we obviously want them not for all vcpus of the L1
hypervisor, but for those of the current guest.
So I think just drop that patch for now. We can dig it out later in case > nesting wants it again.