From: "Keith Packard" via <qemu-devel@nongnu.org>
To: Richard Henderson <richard.henderson@linaro.org>,
Alistair Francis <alistair23@gmail.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Laurent Vivier <laurent@vivier.eu>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
"open list:RISC-V" <qemu-riscv@nongnu.org>
Subject: Re: [PATCH] riscv: Add semihosting support [v8]
Date: Mon, 26 Oct 2020 14:06:20 -0700 [thread overview]
Message-ID: <87a6w8hf3n.fsf@keithp.com> (raw)
In-Reply-To: <32eb3f3a-1256-ac68-c2ad-e887269ee796@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 368 bytes --]
Richard Henderson <richard.henderson@linaro.org> writes:
> This is no different to EXCP_DEBUG, really, which is also internal to qemu but
> user-visible in the same way. Just adjust the logging in riscv_cpu_do_interrupt.
I think that's already handled by the early return in
riscv_cpu_do_interrupt after handling the RISCV_EXCP_SEMIHOST case.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-10-26 21:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 21:49 [PATCH] riscv: Add semihosting support [v8] Keith Packard via
2020-10-24 0:22 ` Alistair Francis
2020-10-24 5:56 ` Keith Packard via
2020-10-24 15:00 ` Alistair Francis
2020-10-26 19:26 ` Richard Henderson
2020-10-26 21:06 ` Keith Packard via [this message]
2020-10-26 19:22 ` Richard Henderson
2020-10-26 21:20 ` Keith Packard via
-- strict thread matches above, loose matches on Subject: below --
2020-09-17 21:02 [PATCH] riscv: Add semihosting support [v7] Keith Packard via
2020-09-17 21:13 ` [PATCH] riscv: Add semihosting support [v8] Keith Packard via
2020-09-17 21:18 ` no-reply
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=87a6w8hf3n.fsf@keithp.com \
--to=qemu-devel@nongnu.org \
--cc=Alistair.Francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=keithp@keithp.com \
--cc=laurent@vivier.eu \
--cc=palmer@dabbelt.com \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sagark@eecs.berkeley.edu \
/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).