From: Yang Weijiang <weijiang.yang@intel.com>
To: seanjc@google.com, pbonzini@redhat.com
Cc: kvm@vger.kernel.org, Yang Weijiang <weijiang.yang@intel.com>
Subject: [kvm-unit-tests PATCH v2 0/3] Fix test failures caused by CET KVM series
Date: Wed, 13 Sep 2023 19:50:03 -0400 [thread overview]
Message-ID: <20230913235006.74172-1-weijiang.yang@intel.com> (raw)
CET KVM series causes sereral test cases fail due to:
1) New introduced constraints between CR0.WP and CR4.CET bits, i.e., setting
CR4.CET == 1 fails if CR0.WP == 0, and setting CR0.WP == 0 fails if CR4.CET
== 1
2) New introduced support of VMX_BASIC[bit56], i.e., skipping HW consistent
check for event error code if the bit is set.
Opportunistically rename related struct and variable to avoid confusion.
Yang Weijiang (3):
x86: VMX: Exclude CR4.CET from the test_vmxon_bad_cr()
x86: VMX: Rename union vmx_basic and related global variable
x86:VMX: Introduce new vmx_basic MSR feature bit for vmx tests
x86/vmx.c | 46 +++++++++++++++++++++++-----------------------
x86/vmx.h | 7 ++++---
x86/vmx_tests.c | 31 ++++++++++++++++++++++---------
3 files changed, 49 insertions(+), 35 deletions(-)
--
2.27.0
next reply other threads:[~2023-09-14 2:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 23:50 Yang Weijiang [this message]
2023-09-13 23:50 ` [kvm-unit-tests PATCH v2 1/3] x86: VMX: Exclude CR4.CET from the test_vmxon_bad_cr() Yang Weijiang
2023-09-13 23:50 ` [kvm-unit-tests PATCH v2 2/3] x86: VMX: Rename union vmx_basic and related global variable Yang Weijiang
2023-09-13 23:50 ` [kvm-unit-tests PATCH v2 3/3] x86:VMX: Introduce new vmx_basic MSR feature bit for vmx tests Yang Weijiang
2023-09-20 15:44 ` [kvm-unit-tests PATCH v2 0/3] Fix test failures caused by CET KVM series Paolo Bonzini
2024-01-29 2:30 ` Yang, Weijiang
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=20230913235006.74172-1-weijiang.yang@intel.com \
--to=weijiang.yang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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.