On Thu, May 28, 2020 at 06:29:44PM +0200, Vitaly Kuznetsov wrote: > Paolo Bonzini <pbonzini@xxxxxxxxxx> writes: > > > Support for guest-MAXPHYADDR < host-MAXPHYADDR is not upstream yet, > > it should not be enabled. Otherwise, all the pde.36 and pte.36 > > fail and the test takes so long that it times out. > > > > Reported-by: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> > > Signed-off-by: Paolo Bonzini <pbonzini@xxxxxxxxxx> > > --- > > x86/unittests.cfg | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/x86/unittests.cfg b/x86/unittests.cfg > > index bf0d02e..d658bc8 100644 > > --- a/x86/unittests.cfg > > +++ b/x86/unittests.cfg > > @@ -116,7 +116,7 @@ extra_params = -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline_immed > > [access] > > file = access.flat > > arch = x86_64 > > -extra_params = -cpu host,phys-bits=36 > > +extra_params = -cpu host > > > > [smap] > > file = smap.flat > > Works both VMX and SVM, thanks! What's the status of the "guest-MAXPHYADDR < host-MAXPHYADDR" work? I ask because the AC_PTE_BIT51 and AC_PDE_BIT51 subtests are broken on CPUs with 52 bit PAs. Is it worth sending a patch to temporarily disable those tests if MAXPHYADDR=52?
