From: Cathy Avery <cavery@redhat.com>
To: kvm@vger.kernel.org
Cc: seanjc@google.com
Subject: [kvm-unit-tests v3 PATCH 0/3] vmx: Fix EPT accessed and dirty flag test
Date: Wed, 16 Feb 2022 12:01:46 -0500 [thread overview]
Message-ID: <20220216170149.25792-1-cavery@redhat.com> (raw)
Fixes to EPT test plus improvements to test_vmx_vmlaunch reporting.
* Changes in v3:
- Split fixes into 3 patches.
- Provide more detailed patch descriptions.
- Improve change log entries.
* Changes in v2:
- Use the saved EPTP to restore the EPTP after each sub-test instead of
manually unwinding what was done by the sub-test, which is error prone
and hard to follow
- Explicitly setup a dummy EPTP, as calling the test in isolation will cause
test failures due to lack a good starting EPTP
- Cleanup test_vmx_vmlaunch to generate clearer and
more consolidated test reports.
New format suggested by seanjc@google.com
Cathy Avery (3):
vmx: Cleanup test_vmx_vmlaunch to generate clearer and more
consolidated test reports
vmx: Explicitly setup a dummy EPTP in EPT accessed and dirty flag test
vmx: Correctly refresh EPTP value in EPT accessed and dirty flag test
x86/vmx_tests.c | 39 +++++++++++++++++++++++----------------
1 file changed, 23 insertions(+), 16 deletions(-)
--
2.31.1
next reply other threads:[~2022-02-16 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 17:01 Cathy Avery [this message]
2022-02-16 17:01 ` [kvm-unit-tests v3 PATCH 1/3] vmx: Cleanup test_vmx_vmlaunch to generate clearer and more consolidated test reports Cathy Avery
2022-02-17 0:56 ` Sean Christopherson
2022-02-16 17:01 ` [kvm-unit-tests v3 PATCH 2/3] vmx: Explicitly setup a dummy EPTP in EPT accessed and dirty flag test Cathy Avery
2022-02-17 0:56 ` Sean Christopherson
2022-02-16 17:01 ` [kvm-unit-tests v3 PATCH 3/3] vmx: Correctly refresh EPTP value " Cathy Avery
2022-02-17 0:57 ` 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=20220216170149.25792-1-cavery@redhat.com \
--to=cavery@redhat.com \
--cc=kvm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox