qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Liviu Ionescu <ilg@livius.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: qemu-system-aarch64 hangs in a cortex-a72 test
Date: Mon, 6 Oct 2025 10:55:07 +0100	[thread overview]
Message-ID: <CAFEAcA_h3-iWubDg++jcO6_S_o_Z1-Xm4RMHqLYq8T=1naADug@mail.gmail.com> (raw)
In-Reply-To: <9EF1806D-4C25-4980-B1CA-16616FA8E32F@livius.net>

On Sun, 5 Oct 2025 at 17:55, Liviu Ionescu <ilg@livius.net> wrote:
>
> Hi!
>
> I have a small semihosted test that I use to test the xPack QEMU releases.
>
> The test worked just fine up to 8.2.9, but hangs with 9.0.0 or later, including 10.0.0.

> Any ideas what changed from 8.x to 9.0 to cause this?

Notably 9.0 is the first release which included
commit 59754f85ed, which enforces the architectural
requirement that when the MMU is disabled unaligned
loads and stores must fault. We didn't use to check
that, so bare metal code that was compiled with a
compiler that assumes unaligned accesses are permitted
(or which simply has a bug where it does an unaligned
access not permitted by the C spec) will now take an
exception where it didn't before. (You should be able
to see that in the -d debug logs if it's happening,
or via gdbstub if you put a breakpoint on the exception
entry point.)

If it doesn't look like that's what it's falling over on,
you could try a git bisect of QEMU to pinpoint the
commit where it stopped working.

thanks
-- PMM


  reply	other threads:[~2025-10-06  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-05 16:55 qemu-system-aarch64 hangs in a cortex-a72 test Liviu Ionescu
2025-10-06  9:55 ` Peter Maydell [this message]
2025-10-06 10:04   ` Liviu Ionescu
2025-10-06 10:45     ` Peter Maydell
2025-10-08 20:18       ` Liviu Ionescu

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='CAFEAcA_h3-iWubDg++jcO6_S_o_Z1-Xm4RMHqLYq8T=1naADug@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=ilg@livius.net \
    --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).