From: Jim MacArthur <jim.macarthur@linaro.org>
To: qemu-devel@nongnu.org
Cc: Jim MacArthur <jim.macarthur@linaro.org>
Subject: [PATCH V3 0/4] Basic ASID2 Support
Date: Wed, 26 Nov 2025 12:36:46 +0000 [thread overview]
Message-ID: <20251126124116.351685-1-jim.macarthur@linaro.org> (raw)
Addressed some more review comments - thank you Alex and Richard for the reviews.
Changes in v3:
- Patch 2&3 (was 2):
- Split patch 2 into 2 parts, one enabling FNG1, FNG0, and A2, and another
enabling ASID2 for cpu_max. The patch enabling cpu_max can be dropped or
reverted later if not desired at this time.
- Patch 4 (was 3):
- Check for presence of TCR2_EL1 in test, abort test if not present.
- Additionally test that new fields read as RES0 if ASID2 is not present.
Changes in v2:
- patch 2:
- Added FNG1, FNG0, A2 to mask for tcr2_el2_write
- patch 3:
- Changed test for ASID from "=0x100" to "!= 0"
*** BLURB HERE ***
Jim MacArthur (4):
target/arm: Enable ID_AA64MMFR4_EL1 register.
target/arm: Allow writes to FNG1, FNG0, A2
target/arm/tcg/cpu64.c: Enable ASID2 for cpu_max
tests: Add test for ASID2 and write/read of feature bits
target/arm/cpu-features.h | 7 +++
target/arm/cpu-sysregs.h.inc | 1 +
target/arm/helper.c | 10 ++++-
target/arm/tcg/cpu64.c | 4 ++
tests/tcg/aarch64/system/asid2.c | 75 ++++++++++++++++++++++++++++++++
5 files changed, 95 insertions(+), 2 deletions(-)
create mode 100644 tests/tcg/aarch64/system/asid2.c
--
2.43.0
next reply other threads:[~2025-11-26 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 12:36 Jim MacArthur [this message]
2025-11-26 12:36 ` [PATCH V3 1/4] target/arm: Enable ID_AA64MMFR4_EL1 register Jim MacArthur
2025-11-26 12:36 ` [PATCH V3 2/4] target/arm: Allow writes to FNG1, FNG0, A2 Jim MacArthur
2025-11-26 12:36 ` [PATCH V3 3/4] target/arm/tcg/cpu64.c: Enable ASID2 for cpu_max Jim MacArthur
2025-11-26 12:36 ` [PATCH V3 4/4] tests: Add test for ASID2 and write/read of feature bits Jim MacArthur
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=20251126124116.351685-1-jim.macarthur@linaro.org \
--to=jim.macarthur@linaro.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).