Re: [Xen-devel] [PATCH] x86/hvm: always expose x2APIC feature in max HVM cpuid policy

["Roger Pau Monné" <roger.pau@citrix.com>]

On Tue, Dec 24, 2019 at 12:23:12PM +0000, Andrew Cooper wrote:
> On 24/12/2019 10:18, Roger Pau Monne wrote:
> > On hardware without x2APIC support Xen emulated local APIC will
> > provide such mode, and hence the feature should be set in the maximum
> > HVM cpuid policy.
> >
> > Not exposing it in the maximum policy results in HVM domains not
> > getting such feature exposed unless it's also supported by the
> > underlying hardware.
> >
> > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> 
> x2apic has never been exposed via this mechanism, due to its effects on
> topology calculations.

Well, it's exposed in hvm_max_cpuid_policy if it's present in the
hardware. IMO it's kind of weird that the presence of the x2APIC feature
on the max policy depends on the underlying hardware, when it's always
supported by the emulated vlapic.

I think x2APIC must either always be part of the max policy, or never,
or else it's very easy to cause regressions because it's not so easy
to find a box without x2APIC.

> It has however always been down to the toolstack to opt in, and Xen
> permits this via recalculate_cpuid_policy(), on the expectation that the
> toolstack knew what it was doing WRT topology (all evidence actually to
> the contrary).

Hm, I can try to force the setting in libxc.

> If we're seeing a recent change in behaviour, then it will be from libxc.

IIRC x2APIC was always exposed to HVM guests regardless of the
underlying hardware support.

Thanks, Roger.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel