From: Tim <mdspan.github@gmail.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, richard.henderson@linaro.org,
zhao1.liu@intel.com, Tim <mdspan.github@gmail.com>
Subject: [PATCH 0/4] target/i386: emulate LAM in TCG
Date: Tue, 10 Nov 2026 13:01:04 +0000 [thread overview]
Message-ID: <20261110130108.706228-1-mdspan.github@gmail.com> (raw)
This series emulates LAM in TCG for x86_64 system mode and reports it
in "-cpu max". linux-user support will follow in a separate series.
Patch 1 keeps the CR3 LAM bits out of the PML5 table address. Patch 2
makes the large-page check in tlb_flush_range_locked() compare under
the flush mask, as agreed in [2]. Patch 3 is the LAM emulation, and
patch 4 adds a system-mode test.
The design follows the RFC thread [1]:
- On a TLB miss, get_physical_address() masks the address and runs
the canonical check and the page walk on the result. The entry is
installed under the tagged address, so each tag of a page has its
own entry. INVLPG and INVLPGA flush every tagged alias with
tlb_flush_page_bits_by_mmuidx(), and a change of CR4.LAM_SUP
flushes the TLB.
- Instruction fetches are not masked. If masking changes the address,
an entry filled by a data access is not executable, and an entry filled
by a fetch is not readable or writable.
- Exceptions do not report the tagged address, which answers
Richard's question [3]. On #PF, CR2 receives the masked address
(SDM Vol. 3A, section 4.4.3), and #GP reports no address.
- gdbstub, monitor, and qemu_plugin_translate_vaddr() translate a
tagged address as a data access does.
Known gaps:
- Data breakpoints on an untagged address do not fire for accesses
through a tagged alias.
- With LAM_U48 and 5-level paging, gdbstub, monitor, and
qemu_plugin_translate_vaddr() translate an instruction address at
or above 2^47 as a data address, not as a fetch does.
[1] https://lists.nongnu.org/archive/html/qemu-devel/2026-10/msg01840.html
[2] https://lists.nongnu.org/archive/html/qemu-devel/2026-11/msg01599.html
[3] https://lists.nongnu.org/archive/html/qemu-devel/2026-10/msg05620.html
Tim (4):
target/i386: mask the PML5 table address taken from CR3
accel/tcg: compare large pages under the flush mask
target/i386: emulate LAM in TCG
tests/tcg/x86_64: add a LAM system test
accel/tcg/cputlb.c | 4 +-
target/i386/cpu.c | 2 +-
target/i386/cpu.h | 46 ++
target/i386/helper.c | 8 +-
target/i386/tcg/system/excp_helper.c | 33 +-
target/i386/tcg/system/misc_helper.c | 24 +-
target/i386/tcg/system/svm_helper.c | 3 +-
tests/tcg/x86_64/system/boot.S | 14 +
tests/tcg/x86_64/system/lam.c | 797 +++++++++++++++++++++++++++
tests/tcg/x86_64/system/meson.build | 15 +
10 files changed, 934 insertions(+), 12 deletions(-)
create mode 100644 tests/tcg/x86_64/system/lam.c
--
2.47.3
next reply other threads:[~2026-11-10 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 13:01 Tim [this message]
2026-11-10 13:01 ` [PATCH 1/4] target/i386: mask the PML5 table address taken from CR3 Tim
2026-11-10 13:01 ` [PATCH 2/4] accel/tcg: compare large pages under the flush mask Tim
2026-11-10 13:01 ` [PATCH 3/4] target/i386: emulate LAM in TCG Tim
2026-11-13 18:12 ` Richard Henderson
2026-11-10 13:01 ` [PATCH 4/4] tests/tcg/x86_64: add a LAM system test Tim
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=20261110130108.706228-1-mdspan.github@gmail.com \
--to=mdspan.github@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=zhao1.liu@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