From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Mark Langsdorf" <mark.langsdorf@calxeda.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Fabien Chouteau" <chouteau@adacore.com>,
"Alexander Graf" <agraf@suse.de>,
"Blue Swirl" <blauwirbel@gmail.com>,
"Michael Walle" <michael@walle.cc>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Paul Brook" <paul@codesourcery.com>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"open list:New World" <qemu-ppc@nongnu.org>,
"Andreas Färber" <andreas.faerber@web.de>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] turn firmware image filename into a machine option
Date: Tue, 01 Oct 2013 17:05:13 +0200 [thread overview]
Message-ID: <1380639913.5280.72.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <CAFEAcA9jvmSDLxYqsATD9gNvohmf0EP1p6YiWSnJ-sYfUM5+sw@mail.gmail.com>
On Di, 2013-10-01 at 22:00 +0900, Peter Maydell wrote:
> On 1 October 2013 21:16, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > Hi,
> >
> >> -bios we're stuck with because it's a legacy
> >> option,
> >
> > What is legacy about it?
>
> The fact that we've had it since forever, it was introduced for
> a specific x86 use case and has since accreted behaviour
> rather than being designed.
The x86 use case is where the x86 centric name comes from. But that's
it. Almost every machine has some kind of firmware which does the
initialization, that certainly isn't a x86-only / legacy concept ...
> >> >> Why is this a machine option rather than a property of
> >> >> the ROM/flash device?
> >> >
> >> > Not all machines have a flash device.
> >>
> >> No, but they must have *something* that the firmware code lives in...
> >
> > Some don't. They just memcpy the firmware into guest ram instead.
>
> ...is that a good thing? What does the real hardware do? Should we
> be doing that instead? Isn't this awkward on reset?
Isn't ideal of course. But it is how it is, for whatever reasons, and
I'm not going to implement proper rom/flash emulation for each and every
qemu machine type.
I just need some way to have different default firmware images for
different pc machine type versions. Requests to considering other
firmware loading needs (such as the two images needed for sPAPR) when
doing this is reasonable. Blaming me for how inconistent qemu's
firmware loading is today is not ok.
> > Given that pflash operates on a blockdev I don't see a obvious way to
> > change that ...
>
> We could make pflash accept a plain file which is then used as the
> read-only initialization for a blockdev which isn't backed by anything,
> for example.
Magically creating something for users convenience (blkdev in this case)
isn't without problems. I did that with usb-storage, which creates a
second device (scsi-disk) automatically. Caused all sorts of trouble
later on. Don't feel like repeating that mistake.
cheers,
Gerd
next prev parent reply other threads:[~2013-10-01 15:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 9:39 [Qemu-devel] [PATCH] turn firmware image filename into a machine option Gerd Hoffmann
2013-10-01 10:55 ` Peter Maydell
2013-10-01 11:22 ` Gerd Hoffmann
2013-10-01 11:32 ` Peter Maydell
2013-10-01 12:16 ` Gerd Hoffmann
2013-10-01 12:20 ` Andreas Färber
2013-10-01 13:41 ` Gerd Hoffmann
2013-10-01 13:46 ` Andreas Färber
2013-10-01 14:23 ` Alexey Kardashevskiy
2013-10-01 14:40 ` Gerd Hoffmann
2013-10-01 14:45 ` Alexander Graf
2013-10-01 21:23 ` Benjamin Herrenschmidt
2013-10-02 1:18 ` Alexey Kardashevskiy
2013-10-01 13:00 ` Peter Maydell
2013-10-01 14:57 ` Paolo Bonzini
2013-10-01 15:05 ` Gerd Hoffmann [this message]
2013-10-01 15:12 ` Peter Maydell
2013-10-01 15:28 ` Paolo Bonzini
2013-10-01 15:42 ` Anthony Liguori
[not found] ` <524AB29F.3030906@suse.de>
2013-10-01 13:32 ` Gerd Hoffmann
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=1380639913.5280.72.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=anthony@codemonkey.ws \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=chouteau@adacore.com \
--cc=hpoussin@reactos.org \
--cc=mark.langsdorf@calxeda.com \
--cc=michael@walle.cc \
--cc=paul@codesourcery.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rth@twiddle.net \
/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).