From: Anthony Liguori <anthony@codemonkey.ws>
To: Jordan Justen <jljusten@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Jordan Justen <jordan.l.justen@intel.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4] hw/pc: Support system flash memory with -pflash parameter
Date: Sat, 23 Jul 2011 19:56:01 -0500 [thread overview]
Message-ID: <4E2B6DA1.2050805@codemonkey.ws> (raw)
In-Reply-To: <CAFe8ug-_M_B93L0RGAXxeV3pAjk4tKfD6ho7v4ahtWqRNT715A@mail.gmail.com>
On 07/23/2011 07:18 PM, Jordan Justen wrote:
>> In terms of other flash devices, I don't think it's that simple. Flash is
>> tied to the mobo layout so I don't think index> 0 really makes sense unless
>> you allow a specific mapping address. I doubt that's terribly useful.
>
> I think VM's have a different situation than real hardware. I'm not
> sure an all ROM or all flash decision will work well for qemu. In
> most cases it may work better to make a ROM image available just below
> 4GB, and add a flash image below this ROM.
>
> This allows the qemu's firmware to be updated as usual in
> ${prefix}/share/bios.bin, but still allows a flash memory to be
> available below this. (The flash below the ROM could be used only for
> storing UEFI variables.)
>
> Otherwise when a new qemu is released along with a new firmware image,
> the VM instance using writable flash will continue to use the old
> firmware image.
Yes, that's a feature.
We could have a second nvram for other purposes of course. That could
be defined as index=1.
Regards,
Anthony Liguori
prev parent reply other threads:[~2011-07-24 0:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 19:37 [Qemu-devel] [PATCH v4] hw/pc: Support system flash memory with -pflash parameter Jordan Justen
2011-07-16 0:16 ` Jordan Justen
2011-07-23 15:51 ` Anthony Liguori
2011-07-23 20:19 ` Jordan Justen
2011-07-23 21:25 ` Anthony Liguori
2011-07-23 22:06 ` Jordan Justen
2011-07-23 22:26 ` Anthony Liguori
2011-07-24 0:18 ` Jordan Justen
2011-07-24 0:56 ` Anthony Liguori [this message]
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=4E2B6DA1.2050805@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jljusten@gmail.com \
--cc=jordan.l.justen@intel.com \
--cc=kwolf@redhat.com \
--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.