From: Peter Maydell <peter.maydell@linaro.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Thomas Huth <thuth@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-devel <qemu-devel@nongnu.org>,
Cornelia Huck <conny@cornelia-huck.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: VW ELF loader
Date: Mon, 10 Feb 2020 10:37:19 +0000 [thread overview]
Message-ID: <CAFEAcA9uOT-M=yfPSv49mLSVoPOXDsp0MBCxXfAN=ctjKHv6XA@mail.gmail.com> (raw)
In-Reply-To: <20200210073008.GE22584@umbus.fritz.box>
On Mon, 10 Feb 2020 at 07:56, David Gibson <david@gibson.dropbear.id.au> wrote:
> On Fri, Feb 07, 2020 at 12:45:20AM +0100, Paolo Bonzini wrote:
> > Every platform that QEMU supports is just using a firmware to do
> > firmware things; it can be U-Boot, EDK-2, SLOF, SeaBIOS, qboot, with
> > varying level of complexity. Some are doing -kernel in QEMU rather than
> > firmware, but that's where things end.
>
> Well, yeah, but AIUI those platforms actually have a defined hardware
> environment on which the firmware is running. For PAPR we don't, we
> *only* have a specification for the "hardware"+"firmware" environment
> as seen by the OS together.
(The below is not intended to be a prescription for what PPC should
do, just some background info about what we're doing with Arm currently.)
For Arm our 'virt' board is drifting a bit towards doing some 'firmware'
ABIs in QEMU -- currently this mostly means PSCI (for CPU power on/off,
system reset, etc), but there have been proposals for other firmware
ABIs that are hard to implement in guest firmware. I tend to agree with
Paolo in principle that where possible keeping QEMU to "we implement
some hardware emulation" and having firmware running in the guest
is a nicer separation of concerns, though, so for Arm I'd like
to avoid ending up with a lot of firmware-equivalent code in QEMU.
FWIW for the Arm 'virt' board there is no defined hardware spec
in the "handed down from elsewhere" sense -- so we defined our
own (and some mechanisms for passing the device tree description
of it into the guest firmware).
thanks
-- PMM
next prev parent reply other threads:[~2020-02-10 10:38 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 13:39 VW ELF loader Alexey Kardashevskiy
2020-02-01 19:04 ` Paolo Bonzini
2020-02-02 11:51 ` Alexey Kardashevskiy
2020-02-02 17:38 ` Paolo Bonzini
2020-02-03 1:31 ` David Gibson
2020-02-03 1:28 ` David Gibson
2020-02-03 9:12 ` Paolo Bonzini
2020-02-03 9:50 ` David Gibson
2020-02-03 10:58 ` Alexey Kardashevskiy
2020-02-03 15:08 ` Paolo Bonzini
2020-02-03 22:36 ` Alexey Kardashevskiy
2020-02-03 22:56 ` Paolo Bonzini
2020-02-03 23:19 ` Alexey Kardashevskiy
2020-02-03 23:26 ` Paolo Bonzini
2020-02-04 6:16 ` Thomas Huth
2020-02-04 8:54 ` Cornelia Huck
2020-02-04 9:20 ` Restrictions of libnet (was: Re: VW ELF loader) Thomas Huth
2020-02-04 9:32 ` Thomas Huth
2020-02-04 9:33 ` Michal Suchánek
2020-02-05 5:30 ` David Gibson
2020-02-05 6:24 ` Thomas Huth
2020-02-10 7:55 ` David Gibson
2020-02-10 9:39 ` Michal Suchánek
2020-02-13 3:16 ` David Gibson
2020-02-04 23:18 ` VW ELF loader Alexey Kardashevskiy
2020-02-05 6:06 ` David Gibson
2020-02-05 9:28 ` Cornelia Huck
2020-02-06 4:47 ` David Gibson
2020-02-06 8:27 ` Paolo Bonzini
2020-02-06 23:17 ` Alexey Kardashevskiy
2020-02-06 23:45 ` Paolo Bonzini
2020-02-10 7:30 ` David Gibson
2020-02-10 10:37 ` Peter Maydell [this message]
2020-02-10 11:25 ` Paolo Bonzini
2020-02-14 3:23 ` David Gibson
2020-02-10 7:28 ` David Gibson
2020-02-10 11:26 ` Paolo Bonzini
2020-02-14 4:02 ` David Gibson
2020-02-05 5:58 ` David Gibson
2020-02-06 8:29 ` Paolo Bonzini
2020-02-06 23:23 ` Alexey Kardashevskiy
2020-02-06 23:46 ` Paolo Bonzini
2020-02-10 0:31 ` Alexey Kardashevskiy
2020-02-13 1:43 ` Alexey Kardashevskiy
2020-02-13 10:17 ` Paolo Bonzini
2020-02-14 0:01 ` Alexey Kardashevskiy
2020-02-14 2:30 ` David Gibson
2020-02-04 9:40 ` Christian Borntraeger
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='CAFEAcA9uOT-M=yfPSv49mLSVoPOXDsp0MBCxXfAN=ctjKHv6XA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=aik@ozlabs.ru \
--cc=borntraeger@de.ibm.com \
--cc=conny@cornelia-huck.de \
--cc=david@gibson.dropbear.id.au \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=thuth@redhat.com \
/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).