From: Sean Christopherson <seanjc@google.com>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [kvm-unit-tests PATCH 0/5] Collection of tests for canonical checks on LA57 enabled CPUs
Date: Fri, 14 Feb 2025 13:25:23 -0800 [thread overview]
Message-ID: <Z6-0wxPyAvLg9FRi@google.com> (raw)
In-Reply-To: <20240907005440.500075-1-mlevitsk@redhat.com>
On Fri, Sep 06, 2024, Maxim Levitsky wrote:
> This is a set of tests that checks KVM and CPU behaviour in regard to
> canonical checks of various msrs, segment bases, instructions that
> were found to ignore CR4.LA57 on CPUs that support 5 level paging.
I have a variety of comments, but nothing that meaningfully changes the
functionality of the testcases (mostly cosmetic stuff). I have very limited
cycles for KUT right now, so I'm going to send a v2 with my changes, but I'll
respond to each patch with my feedback/changes. Please holler if anything is
too objectionable.
> Maxim Levitsky (5):
> x86: add _safe and _fep_safe variants to segment base load
> instructions
> x86: add a few functions for gdt manipulation
> x86: move struct invpcid_desc descriptor to processor.h
> Add a test for writing canonical values to various msrs and fields
> nVMX: add a test for canonical checks of various host state vmcs12
> fields.
>
> lib/x86/desc.c | 39 ++++-
> lib/x86/desc.h | 9 +-
> lib/x86/msr.h | 42 ++++++
> lib/x86/processor.h | 58 +++++++-
> x86/Makefile.x86_64 | 1 +
> x86/canonical_57.c | 346 ++++++++++++++++++++++++++++++++++++++++++++
> x86/pcid.c | 6 -
> x86/vmx_tests.c | 183 +++++++++++++++++++++++
There's no unittest.cfg change, which makes it annoyingly difficult to run the
new tests.
And there's already kinda sorta an LA57 test, la57.c, which just needs minor
tweaking to play nice with x86-64, so I think the easiest approach is to modify
la57.c to run on x86-64 and then lands these testcases there.
> 8 files changed, 667 insertions(+), 17 deletions(-)
> create mode 100644 x86/canonical_57.c
next prev parent reply other threads:[~2025-02-14 21:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 0:54 [kvm-unit-tests PATCH 0/5] Collection of tests for canonical checks on LA57 enabled CPUs Maxim Levitsky
2024-09-07 0:54 ` [kvm-unit-tests PATCH 1/5] x86: add _safe and _fep_safe variants to segment base load instructions Maxim Levitsky
2024-09-07 0:54 ` [kvm-unit-tests PATCH 2/5] x86: add a few functions for gdt manipulation Maxim Levitsky
2024-09-07 0:54 ` [kvm-unit-tests PATCH 3/5] x86: move struct invpcid_desc descriptor to processor.h Maxim Levitsky
2024-09-07 0:54 ` [kvm-unit-tests PATCH 4/5] Add a test for writing canonical values to various msrs and fields Maxim Levitsky
2025-02-14 22:00 ` Sean Christopherson
2024-09-07 0:54 ` [kvm-unit-tests PATCH 5/5] nVMX: add a test for canonical checks of various host state vmcs12 fields Maxim Levitsky
2025-02-14 22:08 ` Sean Christopherson
2024-11-03 21:08 ` [kvm-unit-tests PATCH 0/5] Collection of tests for canonical checks on LA57 enabled CPUs Maxim Levitsky
2024-11-22 1:31 ` Maxim Levitsky
2024-12-14 0:19 ` Maxim Levitsky
2025-02-14 21:25 ` Sean Christopherson [this message]
2025-02-24 17:23 ` Sean Christopherson
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=Z6-0wxPyAvLg9FRi@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox