From: Sean Christopherson <seanjc@google.com>
To: John Sperbeck <jsperbeck@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: selftests: use X86_MEMTYPE_WB instead of VMX_BASIC_MEM_TYPE_WB
Date: Wed, 6 Nov 2024 06:29:16 -0800 [thread overview]
Message-ID: <Zyt9PPB5AGE73HHC@google.com> (raw)
In-Reply-To: <20241106034031.503291-1-jsperbeck@google.com>
On Tue, Nov 05, 2024, John Sperbeck wrote:
> In 08a7d2525511 ("tools arch x86: Sync the msr-index.h copy with the
> kernel sources"), VMX_BASIC_MEM_TYPE_WB was removed. Use X86_MEMTYPE_WB
> instead.
Drat. For all my talk about KVM selftests not caring about kernel headers, that's
obviously not entirely true. Most of the selftests code is standalone, e.g. CR4
and xfeature bits are all manually defined. But redefining the myriad MSR #defines
does seem like a complete waste of time and effort.
> Fixes: 08a7d2525511 ("tools arch x86: Sync the msr-index.h copy with the
> kernel sources")
Unnecessary newline, i.e. don't wrap metadata tags.
> Signed-off-by: John Sperbeck <jsperbeck@google.com>
Acked-by: Sean Christopherson <seanjc@google.com>
Paolo, can you grab this for 6.12-rc7? And fixup the Fixes. I'll mention this
again in the pull request I have planned for later today.
> ---
> tools/testing/selftests/kvm/lib/x86_64/vmx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/kvm/lib/x86_64/vmx.c b/tools/testing/selftests/kvm/lib/x86_64/vmx.c
> index 089b8925b6b2..d7ac122820bf 100644
> --- a/tools/testing/selftests/kvm/lib/x86_64/vmx.c
> +++ b/tools/testing/selftests/kvm/lib/x86_64/vmx.c
> @@ -200,7 +200,7 @@ static inline void init_vmcs_control_fields(struct vmx_pages *vmx)
> if (vmx->eptp_gpa) {
> uint64_t ept_paddr;
> struct eptPageTablePointer eptp = {
> - .memory_type = VMX_BASIC_MEM_TYPE_WB,
> + .memory_type = X86_MEMTYPE_WB,
> .page_walk_length = 3, /* + 1 */
> .ad_enabled = ept_vpid_cap_supported(VMX_EPT_VPID_CAP_AD_BITS),
> .address = vmx->eptp_gpa >> PAGE_SHIFT_4K,
> --
> 2.47.0.277.g8800431eea-goog
>
next prev parent reply other threads:[~2024-11-06 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 3:40 [PATCH] KVM: selftests: use X86_MEMTYPE_WB instead of VMX_BASIC_MEM_TYPE_WB John Sperbeck
2024-11-06 14:29 ` Sean Christopherson [this message]
2024-11-08 9:02 ` Paolo Bonzini
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=Zyt9PPB5AGE73HHC@google.com \
--to=seanjc@google.com \
--cc=acme@redhat.com \
--cc=jsperbeck@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.