From: Manali Shukla <manali.shukla@amd.com>
To: Yosry Ahmed <yosry.ahmed@linux.dev>,
Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Kevin Cheng <chengkev@google.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 03/14] x86/svm: Cleanup selective cr0 write intercept test
Date: Wed, 12 Nov 2025 19:18:28 +0530 [thread overview]
Message-ID: <3cbc2be4-11f4-4ff2-989c-8bf7083c0f0e@amd.com> (raw)
In-Reply-To: <20251110232642.633672-4-yosry.ahmed@linux.dev>
On 11/11/2025 4:56 AM, Yosry Ahmed wrote:
> Rename the test and functions to more general names describing the test
> more accurately. Use X86_CR0_CD instead of hardcoding the bitmask, and
> explicitly clear the bit in the prepare() function to make it clearer
> that it would only be set by the test.
>
> Signed-off-by: Yosry Ahmed <yosry.ahmed@linux.dev>
> ---
> x86/svm_tests.c | 22 +++++++++-------------
> 1 file changed, 9 insertions(+), 13 deletions(-)
>
> diff --git a/x86/svm_tests.c b/x86/svm_tests.c
> index 80d5aeb108650..e911659194b3d 100644
> --- a/x86/svm_tests.c
> +++ b/x86/svm_tests.c
> @@ -793,23 +793,19 @@ static bool check_asid_zero(struct svm_test *test)
> return vmcb->control.exit_code == SVM_EXIT_ERR;
> }
>
> -static void sel_cr0_bug_prepare(struct svm_test *test)
> +static void prepare_sel_cr0_intercept(struct svm_test *test)
> {
> + vmcb->save.cr0 &= ~X86_CR0_CD;
> vmcb->control.intercept |= (1ULL << INTERCEPT_SELECTIVE_CR0);
> }
>
> -static bool sel_cr0_bug_finished(struct svm_test *test)
> -{
> - return true;
> -}
> -
> -static void sel_cr0_bug_test(struct svm_test *test)
> +static void test_sel_cr0_write_intercept(struct svm_test *test)
> {
> unsigned long cr0;
>
> - /* read cr0, clear CD, and write back */
> + /* read cr0, set CD, and write back */
> cr0 = read_cr0();
> - cr0 |= (1UL << 30);
> + cr0 |= X86_CR0_CD;
> write_cr0(cr0);
>
> /*
> @@ -821,7 +817,7 @@ static void sel_cr0_bug_test(struct svm_test *test)
> exit(report_summary());
> }
>
> -static bool sel_cr0_bug_check(struct svm_test *test)
> +static bool check_sel_cr0_intercept(struct svm_test *test)
> {
> return vmcb->control.exit_code == SVM_EXIT_CR0_SEL_WRITE;
> }
> @@ -3486,9 +3482,9 @@ struct svm_test svm_tests[] = {
> { "asid_zero", default_supported, prepare_asid_zero,
> default_prepare_gif_clear, test_asid_zero,
> default_finished, check_asid_zero },
> - { "sel_cr0_bug", default_supported, sel_cr0_bug_prepare,
> - default_prepare_gif_clear, sel_cr0_bug_test,
> - sel_cr0_bug_finished, sel_cr0_bug_check },
> + { "sel cr0 write intercept", default_supported,
> + prepare_sel_cr0_intercept, default_prepare_gif_clear,
> + test_sel_cr0_write_intercept, default_finished, check_sel_cr0_intercept},
> { "tsc_adjust", tsc_adjust_supported, tsc_adjust_prepare,
> default_prepare_gif_clear, tsc_adjust_test,
> default_finished, tsc_adjust_check },
LGTM
Reviewed-by: Manali Shukla <manali.shukla@amd.com>
Tested on AMD Genoa machine. This test case works as expected.
Tested-by: Manali Shukla <manali.shukla@amd.com>
next prev parent reply other threads:[~2025-11-12 13:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 23:26 [PATCH v3 00/14] Improvements for (nested) SVM testing Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 01/14] scripts: Always return '2' when skipping tests Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 02/14] x86/vmx: Skip vmx_pf_exception_test_fep early if FEP is not available Yosry Ahmed
2025-11-14 0:40 ` Sean Christopherson
2025-11-14 0:47 ` Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 03/14] x86/svm: Cleanup selective cr0 write intercept test Yosry Ahmed
2025-11-12 13:48 ` Manali Shukla [this message]
2025-11-10 23:26 ` [PATCH v3 04/14] x86/svm: Move CR0 selective write intercept test near CR3 intercept Yosry Ahmed
2025-11-12 13:52 ` Manali Shukla
2025-11-10 23:26 ` [PATCH v3 05/14] x86/svm: Add FEP helpers for SVM tests Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 06/14] x86/svm: Report unsupported " Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 07/14] x86/svm: Move report_svm_guest() to the top of svm_tests.c Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 08/14] x86/svm: Print SVM test names before running tests Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 09/14] x86/svm: Deflake svm_tsc_scale_test Yosry Ahmed
2025-11-14 0:34 ` Sean Christopherson
2025-11-14 5:46 ` Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 10/14] x86/svm: Generalize and improve selective CR0 write intercept test Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 11/14] x86/svm: Add more selective CR0 write and LMSW test cases Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 12/14] x86/svm: Cleanup LBRV tests Yosry Ahmed
2025-11-13 11:58 ` Shivansh Dhiman
2025-11-13 14:59 ` Yosry Ahmed
2025-11-14 4:57 ` Shivansh Dhiman
2025-11-14 5:40 ` Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 13/14] x86/svm: Add more LBRV test cases Yosry Ahmed
2025-11-10 23:26 ` [PATCH v3 14/14] x86/svm: Rename VMCB fields to match KVM Yosry Ahmed
2025-11-14 0:40 ` Sean Christopherson
2025-11-11 0:52 ` [PATCH v3 00/14] Improvements for (nested) SVM testing Sean Christopherson
2025-11-11 0:58 ` Yosry Ahmed
2025-11-14 0:46 ` Sean Christopherson
2025-11-14 5:42 ` Yosry Ahmed
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=3cbc2be4-11f4-4ff2-989c-8bf7083c0f0e@amd.com \
--to=manali.shukla@amd.com \
--cc=chengkev@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=yosry.ahmed@linux.dev \
/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