qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, jean-philippe@linaro.org,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	gustavo.romero@linaro.org,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH 0/2] aarch64: update test images with new trusted firmware
Date: Wed, 16 Jul 2025 09:50:37 -0700	[thread overview]
Message-ID: <1de7b0a3-846b-4e7b-b4a7-1b753f61ad0f@linaro.org> (raw)
In-Reply-To: <52c5ed4a-0225-4360-b1c8-e3866041c4b3@linaro.org>

On 7/16/25 9:40 AM, Richard Henderson wrote:
> On 7/15/25 15:23, 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.
>>
>> Pierrick Bouvier (2):
>>     tests/functional/test_aarch64_device_passthrough: update image
>>     tests/functional/test_aarch64_rme: update image
>>
>>    tests/functional/test_aarch64_device_passthrough.py | 9 +++++----
>>    tests/functional/test_aarch64_rme_sbsaref.py        | 9 +++++----
>>    tests/functional/test_aarch64_rme_virt.py           | 9 +++++----
>>    3 files changed, 15 insertions(+), 12 deletions(-)
>>
> 
> Thanks.
> 
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> Tested-by: Richard Henderson <richard.henderson@linaro.org>
> 
> and queued with FEAT_MEC.  I'll re-post at some point closer to opening of the 10.2 tree.
>

Do you plan to merge FEAT_MEC for 10.1, or prefer to wait for 10.2?

> 
> r~



  reply	other threads:[~2025-07-16 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 21:23 [PATCH 0/2] aarch64: update test images with new trusted firmware Pierrick Bouvier
2025-07-15 21:23 ` [PATCH 1/2] tests/functional/test_aarch64_device_passthrough: update image Pierrick Bouvier
2025-07-15 22:08   ` Manos Pitsidianakis
2025-07-15 21:23 ` [PATCH 2/2] tests/functional/test_aarch64_rme: " Pierrick Bouvier
2025-07-16  5:45   ` Manos Pitsidianakis
2025-07-16 16:40 ` [PATCH 0/2] aarch64: update test images with new trusted firmware Richard Henderson
2025-07-16 16:50   ` Pierrick Bouvier [this message]
2025-07-16 18:13     ` Richard Henderson
2025-07-16 18:16       ` Pierrick Bouvier
2025-07-19  4:01 ` Pierrick Bouvier

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=1de7b0a3-846b-4e7b-b4a7-1b753f61ad0f@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=gustavo.romero@linaro.org \
    --cc=jean-philippe@linaro.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --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).