All of lore.kernel.org
 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: AArch64 semihosting?
Date: Thu, 26 May 2022 09:20:46 +0100	[thread overview]
Message-ID: <CAFEAcA-n4GMq1_SCdTDp6sQmHzyyzTk5hav4QqOY3-j3Sr86Jg@mail.gmail.com> (raw)
In-Reply-To: <AADD58D2-C3BE-40DF-8EE5-3A901F4F8F04@livius.net>

On Thu, 26 May 2022 at 09:14, Liviu Ionescu <ilg@livius.net> wrote:
>
> I'm trying to set-up an environment for running unit-tests on AArch64, and I'm constantly getting crashes:
>
> ```
> ilg@wksi ~ % /Users/ilg/Library/xPacks/@xpack-dev-tools/qemu-arm/6.2.0-1.1/.content/bin/qemu-system-aarch64  "--machine" "virt" "--cpu" "cortex-a57" "--kernel" "/Users/ilg/My Files/WKS Projects/micro-os-plus.github/work/aarch64-boot-libgloss/Debug/aarch64-boot-libgloss.elf" "--nographic" "-d" "unimp,guest_errors" "--semihosting-config" "enable=on,target=native" "--semihosting-config" "arg=sample-test,arg=one,arg=two" -s
>
> zsh: segmentation fault   "--machine" "virt" "--cpu" "cortex-a57" "--kernel"  "--nographic" "-d"
> ilg@wksi ~ %
> ```
>
> The application was built with newlib libgloss and all it does is a series of printfs to display Hello World and the argv array.

I'm not aware of any problems with aarch64 semihosting.
If QEMU crashes that's definitely a bug -- can you provide us with
a reproduce case (eg the binary you used here)?

> Some time ago I reworked the semihosting implementation in OpenOCD, and
> there I used a common semihosting implementation for all Arm and RISC-V
> devices; everything worked fine, so a common approach is realistic.

Yes; QEMU also shares code for those two architectures' semihosting
implementation.

thanks
-- PMM


  reply	other threads:[~2022-05-26  8:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  8:14 AArch64 semihosting? Liviu Ionescu
2022-05-26  8:20 ` Peter Maydell [this message]
2022-05-26  8:32   ` Liviu Ionescu
2022-05-26 10:01     ` Peter Maydell
2022-05-26 10:21       ` Peter Maydell
2022-05-26 11:03       ` Liviu Ionescu
2022-05-26 11:08         ` Peter Maydell
2022-05-26 11:46           ` Liviu Ionescu
2022-05-26  8:51   ` 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-n4GMq1_SCdTDp6sQmHzyyzTk5hav4QqOY3-j3Sr86Jg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.