Dom0 doesn't have a toolstack to explicitly decide that ITSC is safe to offer.
For domains which are constructed with disable_migrate set, offer ITSC
automatically.
This is important for HVM-based dom0, and for when cpuid faulting is imposed
on the control domain.
Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
---
CC: Jan Beulich <jbeul...@suse.com>
---
xen/arch/x86/cpuid.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/xen/arch/x86/cpuid.c b/xen/arch/x86/cpuid.c
index 9f16502..bf1eed6 100644
--- a/xen/arch/x86/cpuid.c
+++ b/xen/arch/x86/cpuid.c
@@ -440,6 +440,9 @@ int init_domain_cpuid_policy(struct domain *d)
*d->arch.cpuid = is_pv_domain(d) ? pv_max_policy : hvm_max_policy;
+ if ( d->disable_migrate )
+ d->arch.cpuid->extd.itsc = cpu_has_itsc;
+
recalculate_cpuid_policy(d);
for ( i = 0; i < MAX_CPUID_INPUT; i++ )
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
