From: Liviu Ionescu <ilg@livius.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
keithp@keithp.com, qemu-arm@nongnu.org,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: Semihosting, arm, riscv, ppc and common code
Date: Tue, 14 Jan 2020 09:32:01 +0200 [thread overview]
Message-ID: <AE7841A1-B4D6-4D6D-9AFD-01C4604D7BC4@livius.net> (raw)
In-Reply-To: <11d88b2741eac3f634d5aed9e3355c974b533f7b.camel@kernel.crashing.org>
> On 14 Jan 2020, at 08:25, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> I noticed that the bulk of arm-semi.c (or riscv-semi.c) is trivially
> made completely generic by doing a couple of changes:
Last year I did a similar exercise in OpenOCD, where I took the Arm semihosting code from the Arm specific location, extracted the common part, updated it for latest Arm 64-bit specs, and then used the common code for both Arm and RISC-V.
If you think useful, you might take a look there too.
Regards,
Liviu
next prev parent reply other threads:[~2020-01-14 7:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 6:25 Semihosting, arm, riscv, ppc and common code Benjamin Herrenschmidt
2020-01-14 7:32 ` Liviu Ionescu [this message]
2020-01-14 7:53 ` Benjamin Herrenschmidt
2020-01-14 9:51 ` Alex Bennée
2020-01-15 1:14 ` Benjamin Herrenschmidt
2020-01-15 12:01 ` Alex Bennée
2020-01-15 12:30 ` Liviu Ionescu
2020-01-15 21:28 ` Richard Henderson
2020-01-15 22:02 ` Liviu Ionescu
2020-01-16 2:04 ` Benjamin Herrenschmidt
2020-01-16 7:57 ` Liviu Ionescu
2020-01-16 6:33 ` Benjamin Herrenschmidt
2020-01-14 9:59 ` Peter Maydell
2020-01-15 1:17 ` Benjamin Herrenschmidt
2020-01-15 13:32 ` Peter Maydell
2020-01-16 2:01 ` Benjamin Herrenschmidt
2020-01-16 11:05 ` 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=AE7841A1-B4D6-4D6D-9AFD-01C4604D7BC4@livius.net \
--to=ilg@livius.net \
--cc=alex.bennee@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=keithp@keithp.com \
--cc=pbonzini@redhat.com \
--cc=qemu-arm@nongnu.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).