From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sergio Perez Gonzalez <sergio.perez.gonzalez@intel.com>,
Adriana Cervantes Jimenez <adriana.cervantes.jimenez@intel.com>,
Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH] KVM: selftests: Ignore KVM 5-level paging support for VM_MODE_PXXV48_4K
Date: Tue, 9 Jun 2020 11:54:48 +0200 [thread overview]
Message-ID: <d6a3de35-f4de-9ae9-4467-cadaf679482d@redhat.com> (raw)
In-Reply-To: <20200608181658.GD8223@linux.intel.com>
On 08/06/20 20:16, Sean Christopherson wrote:
> On Thu, May 28, 2020 at 01:55:44PM +0200, Paolo Bonzini wrote:
>> On 28/05/20 04:15, Sean Christopherson wrote:
>>> Explicitly set the VA width to 48 bits for the x86_64-only PXXV48_4K VM
>>> mode instead of asserting the guest VA width is 48 bits. The fact that
>>> KVM supports 5-level paging is irrelevant unless the selftests opt-in to
>>> 5-level paging by setting CR4.LA57 for the guest. The overzealous
>>> assert prevents running the selftests on a kernel with 5-level paging
>>> enabled.
>>>
>>> Incorporate LA57 into the assert instead of removing the assert entirely
>>> as a sanity check of KVM's CPUID output.
>>>
>>> Fixes: 567a9f1e9deb ("KVM: selftests: Introduce VM_MODE_PXXV48_4K")
>>> Reported-by: Sergio Perez Gonzalez <sergio.perez.gonzalez@intel.com>
>>> Cc: Adriana Cervantes Jimenez <adriana.cervantes.jimenez@intel.com>
>>> Cc: Peter Xu <peterx@redhat.com>
>>> Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
>>> ---
>>> tools/testing/selftests/kvm/lib/kvm_util.c | 11 +++++++++--
>>> 1 file changed, 9 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/tools/testing/selftests/kvm/lib/kvm_util.c b/tools/testing/selftests/kvm/lib/kvm_util.c
>>> index c9cede5c7d0de..74776ee228f2d 100644
>>> --- a/tools/testing/selftests/kvm/lib/kvm_util.c
>>> +++ b/tools/testing/selftests/kvm/lib/kvm_util.c
>>> @@ -195,11 +195,18 @@ struct kvm_vm *_vm_create(enum vm_guest_mode mode, uint64_t phy_pages, int perm)
>>> case VM_MODE_PXXV48_4K:
>>> #ifdef __x86_64__
>>> kvm_get_cpu_address_width(&vm->pa_bits, &vm->va_bits);
>>> - TEST_ASSERT(vm->va_bits == 48, "Linear address width "
>>> - "(%d bits) not supported", vm->va_bits);
>>> + /*
>>> + * Ignore KVM support for 5-level paging (vm->va_bits == 57),
>>> + * it doesn't take effect unless a CR4.LA57 is set, which it
>>> + * isn't for this VM_MODE.
>>> + */
>>> + TEST_ASSERT(vm->va_bits == 48 || vm->va_bits == 57,
>>> + "Linear address width (%d bits) not supported",
>>> + vm->va_bits);
>>> pr_debug("Guest physical address width detected: %d\n",
>>> vm->pa_bits);
>>> vm->pgtable_levels = 4;
>>> + vm->va_bits = 48;
>>> #else
>>> TEST_FAIL("VM_MODE_PXXV48_4K not supported on non-x86 platforms");
>>> #endif
>>>
>>
>> Queued, thnaks.
>>
>> Paolo
>
> Looks like this one also got lost in the 5.7 -> 5.8 transition.
>
Indeed, added back to the queue now.
Paolo
prev parent reply other threads:[~2020-06-09 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 2:15 Sean Christopherson
2020-05-28 11:55 ` Paolo Bonzini
2020-06-08 18:16 ` Sean Christopherson
2020-06-09 9:54 ` Paolo Bonzini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6a3de35-f4de-9ae9-4467-cadaf679482d@redhat.com \
--to=pbonzini@redhat.com \
--cc=adriana.cervantes.jimenez@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=sergio.perez.gonzalez@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®