From: Yexuan Yang <yexun@linux.alibaba.com>
To: kvm@vger.kernel.org
Cc: binbin.wu@linux.intel.com, chao.gao@intel.com, seanjc@google.com,
pbonzini@redhat.com, Yexuan Yang <yexun@linux.alibaba.com>
Subject: [kvm-unit-tests PATCH v4] x86/lam: Allocate test page from AREA_LOW instead of AREA_NORMAL
Date: Thu, 16 Jul 2026 18:07:16 +0800 [thread overview]
Message-ID: <20260716100716.1313-1-yexun@linux.alibaba.com> (raw)
The lam test does not set a guest memory size in x86/unittests.cfg, so
QEMU falls back to the default of 128 MiB. AREA_NORMAL starts at PFN
BIT(36-12), i.e. physical 64 GiB, which is never initialized in a
128 MiB guest. As a result, alloc_pages_flags(0, AREA_NORMAL) returns
NULL and test_lam_user() ends up running its LAM checks against a NULL
pointer, which is semantically meaningless even if the metadata-bit
arithmetic happens to succeed.
Allocate from AREA_LOW instead. AREA_LOW_PFN is BIT(24-12) (16 MiB),
well within a 128 MiB guest, and bits 63..47 of the resulting linear
address are still zero, so the LAM48/LAM57 metadata-bit checks remain
valid. Update the adjacent comment accordingly.
Fixes: 0164d7595c85 ("x86: Add test cases for LAM_{U48,U57}")
Signed-off-by: Yexuan Yang <yexun@linux.alibaba.com>
---
v4: Change author information.
v3: Change static_assert to assert.
https://lore.kernel.org/all/20260603015831.41664-1-yexun@linux.alibaba.com/
v2: Assert vaddr instead of pfn.
https://lore.kernel.org/all/20260602060116.35206-1-yexun@linux.alibaba.com/
v1: https://lore.kernel.org/all/20260601035401.39303-1-yexun@linux.alibaba.com/
x86/lam.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/x86/lam.c b/x86/lam.c
index 87efc5dd..63a36539 100644
--- a/x86/lam.c
+++ b/x86/lam.c
@@ -231,13 +231,13 @@ static void test_lam_user(void)
bool has_lam = this_cpu_has(X86_FEATURE_LAM);
/*
- * The physical address of AREA_NORMAL is within 36 bits, so that using
+ * The physical address of AREA_LOW is within 36 bits, so that using
* identical mapping, the linear address will be considered as user mode
* address from the view of LAM, and the metadata bits are not used as
* address for both LAM48 and LAM57.
*/
- vaddr = alloc_pages_flags(0, AREA_NORMAL);
- static_assert((AREA_NORMAL_PFN & GENMASK(63, 47)) == 0UL);
+ vaddr = alloc_pages_flags(0, AREA_LOW);
+ assert(((u64)vaddr & GENMASK(63, 47)) == 0UL);
/*
* Note, LAM doesn't have a global control bit to turn on/off LAM
--
2.54.0
reply other threads:[~2026-07-16 10:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260716100716.1313-1-yexun@linux.alibaba.com \
--to=yexun@linux.alibaba.com \
--cc=binbin.wu@linux.intel.com \
--cc=chao.gao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox