qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: "Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org
Subject: Re: [PULL 15/32] tests/functional/aarch64: add tests for FEAT_RME
Date: Fri, 24 Jan 2025 08:18:56 -0800	[thread overview]
Message-ID: <a5f10050-1914-4f58-a71e-0703ab9a5a19@linaro.org> (raw)
In-Reply-To: <d9094d1e-10bc-4b15-9efe-ebc8bab5d158@redhat.com>

Hi Thomas,

On 1/24/25 05:29, Thomas Huth wrote:
> On 10/01/2025 14.17, Alex Bennée wrote:
>> From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
>>
>> This boot an OP-TEE environment, and launch a nested guest VM inside it
>> using the Realms feature. We do it for virt and sbsa-ref platforms.
> 
>    Hi,
> 
> FWIW, I just saw this test_aarch64_rme_virt test failing once. Looking at
> the console.log, it seems like the guest crashed somewhere at the end of the
> firmware or very early in the kernel:
> 
> EFI stub: Booting Linux Kernel...
> 2025-01-24 13:25:28,226:
> 2025-01-24 13:25:28,226:
> 2025-01-24 13:25:28,227: Synchronous Exception at 0x00000000BF526498
> 2025-01-24 13:25:28,227:
> 2025-01-24 13:25:28,227:
> 2025-01-24 13:25:28,228: Synchronous Exception at 0x00000000BF526498
> 
> I wasn't able to reproduce it afterwards anymore, but in case somebody runs
> into this later again and wonders if it is a later regression: It happened
> for me with commit cf86770c7aa31ebd.
> 
>    Thomas
> 

I met this kind of error before (not on rme), and if I remember well, 
it's coming from EDK2.

We might have a race condition here.

  reply	other threads:[~2025-01-24 16:19 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 13:17 [PULL 00/32] testing updates for 10.0 (tuxrun, libvirt, dockerfiles, misc) Alex Bennée
2025-01-10 13:17 ` [PULL 01/32] tests/functional: update the arm tuxrun tests Alex Bennée
2025-01-10 13:17 ` [PULL 02/32] tests/functional: update the i386 " Alex Bennée
2025-01-10 13:17 ` [PULL 03/32] tests/functional: add a m68k " Alex Bennée
2025-01-10 13:17 ` [PULL 04/32] tests/functional: update the mips32 " Alex Bennée
2025-01-10 13:17 ` [PULL 05/32] tests/functional: update the mips32el " Alex Bennée
2025-01-10 13:17 ` [PULL 06/32] tests/functional: update the mips64 " Alex Bennée
2025-01-10 13:17 ` [PULL 07/32] tests/functional: update the mips64el " Alex Bennée
2025-01-10 13:17 ` [PULL 08/32] tests/functional: update the ppc32 " Alex Bennée
2025-01-10 13:17 ` [PULL 09/32] tests/functional: update the ppc64 " Alex Bennée
2025-01-10 13:17 ` [PULL 10/32] tests/functional: update the riscv32 " Alex Bennée
2025-01-10 13:17 ` [PULL 11/32] tests/functional: update the riscv64 " Alex Bennée
2025-01-10 13:17 ` [PULL 12/32] tests/functional: update the s390x " Alex Bennée
2025-01-10 13:17 ` [PULL 13/32] tests/functional: update the sparc64 " Alex Bennée
2025-01-10 13:17 ` [PULL 14/32] tests/functional: update the x86_64 " Alex Bennée
2025-01-10 13:17 ` [PULL 15/32] tests/functional/aarch64: add tests for FEAT_RME Alex Bennée
2025-01-24 13:29   ` Thomas Huth
2025-01-24 16:18     ` Pierrick Bouvier [this message]
2025-01-25 23:05       ` Alex Bennée
2025-01-10 13:17 ` [PULL 16/32] tests/qtest: remove clock_steps from virtio tests Alex Bennée
2025-01-10 13:17 ` [PULL 17/32] system/qtest: properly feedback results of clock_[step|set] Alex Bennée
2025-01-10 13:17 ` [PULL 18/32] tests/functional: remove hacky sleep from the tests Alex Bennée
2025-01-10 13:17 ` [PULL 19/32] tests/functional: add zstd support to uncompress utility Alex Bennée
2025-01-10 13:17 ` [PULL 20/32] tests/functional: update tuxruntest to use " Alex Bennée
2025-01-10 13:17 ` [PULL 21/32] tests/functional: remove unused kernel_command_line Alex Bennée
2025-01-10 13:17 ` [PULL 22/32] tests/functional: bail aarch64_virt tests early if missing TCG Alex Bennée
2025-01-10 13:17 ` [PULL 23/32] tests/functional: extend test_aarch64_virt with vulkan test Alex Bennée
2025-02-17 16:30   ` Peter Maydell
2025-02-17 17:00     ` Alex Bennée
2025-02-18  6:34     ` Thomas Huth
2025-02-18 10:06       ` Alex Bennée
2025-02-19 13:25   ` Philippe Mathieu-Daudé
2025-02-19 13:43     ` Thomas Huth
2025-02-19 13:52       ` Philippe Mathieu-Daudé
2025-01-10 13:17 ` [PULL 24/32] tests/lcitool: bump to latest version of libvirt-ci Alex Bennée
2025-01-10 13:17 ` [PULL 25/32] tests/docker: move riscv64 cross container from sid to trixie Alex Bennée
2025-01-10 13:17 ` [PULL 26/32] tests/lcitool: remove temp workaround for debian mips64el Alex Bennée
2025-01-10 13:17 ` [PULL 27/32] tests/vm: fix build_path based path Alex Bennée
2025-01-10 13:17 ` [PULL 28/32] tests/vm: partially un-tabify help output Alex Bennée
2025-01-10 13:17 ` [PULL 29/32] tests/vm: allow interactive login as root Alex Bennée
2025-01-10 13:17 ` [PULL 30/32] pc-bios: ensure keymaps dependencies set vnc tests Alex Bennée
2025-01-10 13:17 ` [PULL 31/32] dockerfiles: Remove 'MAINTAINER' entry in debian-tricore-cross.docker Alex Bennée
2025-01-10 13:17 ` [PULL 32/32] MAINTAINERS: Remove myself from reviewers Alex Bennée
2025-01-10 18:38 ` [PULL 00/32] testing updates for 10.0 (tuxrun, libvirt, dockerfiles, misc) Stefan Hajnoczi
2025-01-11 12:16   ` Alex Bennée

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=a5f10050-1914-4f58-a71e-0703ab9a5a19@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).