From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: qemu-devel@nongnu.org
Cc: jean-philippe@linaro.org, richard.henderson@linaro.org,
Leif Lindholm <leif.lindholm@oss.qualcomm.com>,
Peter Maydell <peter.maydell@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
gustavo.romero@linaro.org, qemu-arm@nongnu.org,
Radoslaw Biernacki <rad@semihalf.com>
Subject: Re: [PATCH v2 0/2] aarch64: update test images with new trusted firmware
Date: Fri, 18 Jul 2025 21:00:18 -0700 [thread overview]
Message-ID: <f9e316d7-18c1-4be7-b172-3fe2682e572a@linaro.org> (raw)
In-Reply-To: <20250719035838.2284029-1-pierrick.bouvier@linaro.org>
Hi Richard,
On 7/18/25 8:58 PM, Pierrick Bouvier wrote:
> The FEAT_MEC series [1] introduces FEAT_TCR2 and FEAT_SCTLR2.
> TF-A needs to be aware of that change to allow accesses to those registers, and
> thus must be patched [2] to enable this for QEMU platforms.
>
> Concerned test images need to be updated to allow them to boot.
>
> [1] https://lore.kernel.org/qemu-devel/20250714155836.1514748-1-richard.henderson@linaro.org/
> [2] https://git.codelinaro.org/linaro/dcap/tf-a/trusted-firmware-a/-/commit/c8836cec14213bf92dae79d353bc345254a0a31e
>
> Note: [2] will be upstreamed in TF-A once associated series on QEMU side is
> merged.
>
> v2
> --
>
> - Updated test images with lighter images (only firmwares + kernel + lkvm)
> performing only a Realm boot, and skipping the attestation reporting.
> This does not change what is tested on QEMU side.
> - Build those images automatically on GitHub, and fetch them from there
> directly.
>
> Pierrick Bouvier (2):
> tests/functional/test_aarch64_device_passthrough: update image
> tests/functional/test_aarch64_rme: update image
>
> .../test_aarch64_device_passthrough.py | 27 +++---
> tests/functional/test_aarch64_rme_sbsaref.py | 64 ++++++++------
> tests/functional/test_aarch64_rme_virt.py | 85 +++++++------------
> 3 files changed, 80 insertions(+), 96 deletions(-)
>
please fetch this new version instead of v1, as it contains images that
will be easier for us to maintain in the long term.
Regards,
Pierrick
prev parent reply other threads:[~2025-07-19 4:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 3:58 [PATCH v2 0/2] aarch64: update test images with new trusted firmware Pierrick Bouvier
2025-07-19 3:58 ` [PATCH v2 1/2] tests/functional/test_aarch64_device_passthrough: update image Pierrick Bouvier
2025-07-19 3:58 ` [PATCH v2 2/2] tests/functional/test_aarch64_rme: " Pierrick Bouvier
2025-07-19 10:57 ` Manos Pitsidianakis
2025-07-19 15:38 ` Pierrick Bouvier
2025-07-21 8:31 ` Philippe Mathieu-Daudé
2025-07-19 4:00 ` Pierrick Bouvier [this message]
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=f9e316d7-18c1-4be7-b172-3fe2682e572a@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=gustavo.romero@linaro.org \
--cc=jean-philippe@linaro.org \
--cc=leif.lindholm@oss.qualcomm.com \
--cc=mathieu.poirier@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rad@semihalf.com \
--cc=richard.henderson@linaro.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).