From: Sean Christopherson <seanjc@google.com>
To: Binbin Wu <binbin.wu@linux.intel.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, chao.gao@intel.com,
robert.hu@linux.intel.com
Subject: Re: [kvm-unit-tests PATCH v6 3/4] x86: Add test cases for LAM_{U48,U57}
Date: Wed, 5 Jun 2024 11:53:12 -0700 [thread overview]
Message-ID: <ZmC0GC3wAdiO0Dp2@google.com> (raw)
In-Reply-To: <20240122085354.9510-4-binbin.wu@linux.intel.com>
On Mon, Jan 22, 2024, Binbin Wu wrote:
> +static inline bool lam_u48_active(void)
> +{
> + return (read_cr3() & CR3_LAM_BITS_MASK) == X86_CR3_LAM_U48;
> +}
> +
> +static inline bool lam_u57_active(void)
> +{
> + return !!(read_cr3() & X86_CR3_LAM_U57);
> +}
Same comments as the supervisor patches.
> +static void test_lam_user_mode(bool has_lam, u64 lam_mask, u64 mem, u64 mmio)
> +{
> + unsigned r;
> + bool raised_vector;
> + unsigned long cr3 = read_cr3() & ~CR3_LAM_BITS_MASK;
> + u64 flags = 0;
> +
> + if (is_la57())
> + flags |= FLAGS_LA57;
> +
> + if (has_lam) {
> + if (lam_mask == LAM48_MASK) {
> + r = write_cr3_safe(cr3 | X86_CR3_LAM_U48);
> + report((r == 0) && lam_u48_active(), "Set LAM_U48");
!r is the preferred style
> + } else {
> + r = write_cr3_safe(cr3 | X86_CR3_LAM_U57);
> + report((r == 0) && lam_u57_active(), "Set LAM_U57");
> + }
> + }
> + if (lam_u48_active() || lam_u57_active())
> + flags |= FLAGS_LAM_ACTIVE;
> +
> + run_in_user((usermode_func)test_ptr, GP_VECTOR, flags, lam_mask, mem,
> + false, &raised_vector);
Ah, this is why test_ptr() doesn't recompute things. Hrm. Ah, I think we can at
least compute the mask dynamically, e.g. test_ptr() just need to know if LAM48
and/or LAM57 is enabled, right?
> + run_in_user((usermode_func)test_ptr, GP_VECTOR, flags, lam_mask, mmio,
> + true, &raised_vector);
> +}
next prev parent reply other threads:[~2024-06-05 18:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 8:53 [kvm-unit-tests PATCH v6 0/4] x86: Add test cases for LAM Binbin Wu
2024-01-22 8:53 ` [kvm-unit-tests PATCH v6 1/4] x86: Allow setting of CR3 LAM bits if LAM supported Binbin Wu
2024-01-22 8:53 ` [kvm-unit-tests PATCH v6 2/4] x86: Add test case for LAM_SUP Binbin Wu
2024-06-05 18:24 ` Sean Christopherson
2024-06-18 5:48 ` Binbin Wu
2024-06-18 6:37 ` Binbin Wu
2024-01-22 8:53 ` [kvm-unit-tests PATCH v6 3/4] x86: Add test cases for LAM_{U48,U57} Binbin Wu
2024-06-05 18:53 ` Sean Christopherson [this message]
2024-01-22 8:53 ` [kvm-unit-tests PATCH v6 4/4] x86: Add test case for INVVPID with LAM Binbin Wu
2024-06-05 18:57 ` Sean Christopherson
2024-06-18 5:55 ` Binbin Wu
2024-06-24 8:20 ` Binbin Wu
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=ZmC0GC3wAdiO0Dp2@google.com \
--to=seanjc@google.com \
--cc=binbin.wu@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=robert.hu@linux.intel.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