From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v4 2/3] target/nios2: Move nios2-semi.c to nios2_softmmu_ss
Date: Mon, 20 Jun 2022 15:04:28 -0700 [thread overview]
Message-ID: <f098cca7-cea6-40e9-78b2-46dbf8c40a16@linaro.org> (raw)
In-Reply-To: <CAFEAcA9q6fzATOqHZZ7PZDX_jLiYdc_EsvPEzMqnB+Ehz=uQuQ@mail.gmail.com>
On 6/9/22 03:36, Peter Maydell wrote:
> On Wed, 8 Jun 2022 at 03:43, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> Semihosting is not enabled for nios2-linux-user.
>
> True, but maybe it ought to be (in an ideal world)?
No, I think ideally there'd be no semihosting for user-only.
If you can write to semihosting, you can write to regular syscalls.
Semihosting is good for when we want to do testing of system-mode stuff, and we don't want
the complication of a full os getting in the way.
r~
next prev parent reply other threads:[~2022-06-20 22:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 2:38 [PATCH v4 0/3] target/nios2: semihosting cleanup Richard Henderson
2022-06-08 2:38 ` [PATCH v4 1/3] target/nios2: Eliminate nios2_semi_is_lseek Richard Henderson
2022-06-09 10:33 ` Peter Maydell
2022-06-10 13:33 ` Philippe Mathieu-Daudé via
2022-06-08 2:38 ` [PATCH v4 2/3] target/nios2: Move nios2-semi.c to nios2_softmmu_ss Richard Henderson
2022-06-09 10:36 ` Peter Maydell
2022-06-20 22:04 ` Richard Henderson [this message]
2022-06-21 8:52 ` Peter Maydell
2022-06-10 13:33 ` Philippe Mathieu-Daudé via
2022-06-08 2:38 ` [PATCH v4 3/3] target/nios2: Use semihosting/syscalls.h Richard Henderson
2022-06-09 10:39 ` Peter Maydell
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=f098cca7-cea6-40e9-78b2-46dbf8c40a16@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--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).