All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Liviu Ionescu <ilg@livius.net>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	keithp@keithp.com, qemu-arm@nongnu.org
Subject: Re: Semihosting, arm, riscv, ppc and common code
Date: Tue, 14 Jan 2020 09:51:25 +0000	[thread overview]
Message-ID: <87sgkimkma.fsf@linaro.org> (raw)
In-Reply-To: <cd9a2de94700a2781f176247131dceba690d8f31.camel@kernel.crashing.org>


Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:

> On Tue, 2020-01-14 at 09:32 +0200, Liviu Ionescu wrote:
>> > 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.
>
> Well, one of the LCA talks wasn't that interesting so I started doing
> it and am almost done :-)
>
> I'll look at doing something for arm, riscv and ppc and send patches
> once I get it working.

Cool. Are you considering linux-user as well or are these only things
that make sense for system emulation?

>
> Cheers,
> Ben.
>
>> 
>> Regards,
>> 
>> Liviu


-- 
Alex Bennée

WARNING: multiple messages have this Message-ID (diff)
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Liviu Ionescu <ilg@livius.net>,
	keithp@keithp.com, qemu-arm@nongnu.org, qemu-devel@nongnu.org,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Semihosting, arm, riscv, ppc and common code
Date: Tue, 14 Jan 2020 09:51:25 +0000	[thread overview]
Message-ID: <87sgkimkma.fsf@linaro.org> (raw)
In-Reply-To: <cd9a2de94700a2781f176247131dceba690d8f31.camel@kernel.crashing.org>


Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:

> On Tue, 2020-01-14 at 09:32 +0200, Liviu Ionescu wrote:
>> > 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.
>
> Well, one of the LCA talks wasn't that interesting so I started doing
> it and am almost done :-)
>
> I'll look at doing something for arm, riscv and ppc and send patches
> once I get it working.

Cool. Are you considering linux-user as well or are these only things
that make sense for system emulation?

>
> Cheers,
> Ben.
>
>> 
>> Regards,
>> 
>> Liviu


-- 
Alex Bennée


  reply	other threads:[~2020-01-14  9:51 UTC|newest]

Thread overview: 33+ 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  6:25 ` Benjamin Herrenschmidt
2020-01-14  7:32 ` Liviu Ionescu
2020-01-14  7:32   ` Liviu Ionescu
2020-01-14  7:53   ` Benjamin Herrenschmidt
2020-01-14  7:53     ` Benjamin Herrenschmidt
2020-01-14  9:51     ` Alex Bennée [this message]
2020-01-14  9:51       ` Alex Bennée
2020-01-15  1:14       ` Benjamin Herrenschmidt
2020-01-15  1:14         ` Benjamin Herrenschmidt
2020-01-15 12:01         ` Alex Bennée
2020-01-15 12:01           ` Alex Bennée
2020-01-15 12:30           ` Liviu Ionescu
2020-01-15 12:30             ` Liviu Ionescu
2020-01-15 21:28           ` Richard Henderson
2020-01-15 22:02             ` Liviu Ionescu
2020-01-15 22:02               ` Liviu Ionescu
2020-01-16  2:04               ` Benjamin Herrenschmidt
2020-01-16  2:04                 ` Benjamin Herrenschmidt
2020-01-16  7:57                 ` Liviu Ionescu
2020-01-16  7:57                   ` Liviu Ionescu
2020-01-16  6:33           ` Benjamin Herrenschmidt
2020-01-16  6:33             ` Benjamin Herrenschmidt
2020-01-14  9:59 ` Peter Maydell
2020-01-14  9:59   ` Peter Maydell
2020-01-15  1:17   ` Benjamin Herrenschmidt
2020-01-15  1:17     ` Benjamin Herrenschmidt
2020-01-15 13:32     ` Peter Maydell
2020-01-15 13:32       ` Peter Maydell
2020-01-16  2:01       ` Benjamin Herrenschmidt
2020-01-16  2:01         ` Benjamin Herrenschmidt
2020-01-16 11:05         ` Peter Maydell
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=87sgkimkma.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=benh@kernel.crashing.org \
    --cc=ilg@livius.net \
    --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 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.