From: Chao Gao <chao.gao@intel.com>
To: Binbin Wu <binbin.wu@linux.intel.com>
Cc: <kvm@vger.kernel.org>, <seanjc@google.com>, <pbonzini@redhat.com>,
<robert.hu@linux.intel.com>
Subject: Re: [kvm-unit-tests v3 3/4] x86: Add test cases for LAM_{U48,U57}
Date: Fri, 21 Apr 2023 13:06:03 +0800 [thread overview]
Message-ID: <ZEIZu7Qp5jaYsgLn@chao-email> (raw)
In-Reply-To: <20230412075134.21240-4-binbin.wu@linux.intel.com>
On Wed, Apr 12, 2023 at 03:51:33PM +0800, Binbin Wu wrote:
>This unit test covers:
>1. CR3 LAM bits toggles.
>2. Memory/MMIO access with user mode address containing LAM metadata.
>
>Signed-off-by: Binbin Wu <binbin.wu@linux.intel.com>
Reviewed-by: Chao Gao <chao.gao@intel.com>
two nits below:
>---
>+static void test_lam_user(bool has_lam)
>+{
>+ phys_addr_t paddr;
>+ unsigned long cr3 = read_cr3();
>+
>+ /*
>+ * The physical address width is within 36 bits, so that using identical
>+ * mapping, the linear address will be considered as user mode address
>+ * from the view of LAM.
>+ */
Why 36 bits (i.e., 64G)?
would you mind adding a comment in patch 2 to explain why the virtual
addresses are kernel mode addresses?
>+ paddr = virt_to_phys(alloc_page());
>+ install_page((void *)cr3, paddr, (void *)paddr);
>+ install_page((void *)cr3, IORAM_BASE_PHYS, (void *)IORAM_BASE_PHYS);
are the two lines necessary?
>+
>+ test_lam_user_mode(has_lam, LAM48_MASK, paddr, IORAM_BASE_PHYS);
>+ test_lam_user_mode(has_lam, LAM57_MASK, paddr, IORAM_BASE_PHYS);
>+}
>+
> int main(int ac, char **av)
> {
> bool has_lam;
>@@ -239,6 +309,7 @@ int main(int ac, char **av)
> "use kvm.force_emulation_prefix=1 to enable\n");
>
> test_lam_sup(has_lam, fep_available);
>+ test_lam_user(has_lam);
>
> return report_summary();
> }
>--
>2.25.1
>
next prev parent reply other threads:[~2023-04-21 5:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 7:51 [kvm-unit-tests v3 0/4] x86: Add test cases for LAM Binbin Wu
2023-04-12 7:51 ` [kvm-unit-tests v3 1/4] x86: Allow setting of CR3 LAM bits if LAM supported Binbin Wu
2023-04-21 2:02 ` Chao Gao
2023-04-23 1:42 ` Binbin Wu
2023-04-12 7:51 ` [kvm-unit-tests v3 2/4] x86: Add test case for LAM_SUP Binbin Wu
2023-04-21 3:32 ` Chao Gao
2023-04-12 7:51 ` [kvm-unit-tests v3 3/4] x86: Add test cases for LAM_{U48,U57} Binbin Wu
2023-04-21 5:06 ` Chao Gao [this message]
2023-04-23 3:07 ` Binbin Wu
2023-04-12 7:51 ` [kvm-unit-tests v3 4/4] x86: Add test case for INVVPID with LAM Binbin Wu
2023-04-21 5:38 ` Chao Gao
2023-04-23 3:41 ` Binbin Wu
2023-04-23 6:13 ` 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=ZEIZu7Qp5jaYsgLn@chao-email \
--to=chao.gao@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=robert.hu@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox