On 09/05/2019 18:25, Ankur Arora wrote: > xen_cpuid_base() is used to probe and setup features early in a > guest's lifetime. > > We want this to behave differently depending on xenhost->type: for > instance, local xenhosts cannot intercept the cpuid instruction at all. > > Add op (*cpuid_base)() in xenhost_ops_t. > > Signed-off-by: Ankur Arora <ankur.a.ar...@oracle.com>
What is the real layout of hypervisor nesting here? When Xen is at L0, all HVM guests get working CPUID faulting to combat this problem, because CPUID faulting can be fully emulated even on older Intel hardware, and AMD hardware. It is a far cleaner way of fixing the problem. ~Andrew
