From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Jordan Justen <jljusten@gmail.com>
Cc: Gleb Natapov <gleb@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Michal Suchanek <hramrach@centrum.cz>,
Kevin O'Connor <kevin@koconnor.net>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: RFC: emulation of system flash
Date: Thu, 10 Mar 2011 23:31:27 +0100 [thread overview]
Message-ID: <4D79513F.2090008@gmx.net> (raw)
In-Reply-To: <AANLkTi=_dtWSEvt0+kWozQ4GCHfp1wDfO5StrRESMYhn@mail.gmail.com>
Auf 10.03.2011 23:14, Jordan Justen schrieb:
> On Thu, Mar 10, 2011 at 13:52, Carl-Daniel Hailfinger
> <c-d.hailfinger.devel.2006@gmx.net> wrote:
>
>> Auf 10.03.2011 19:43, Jordan Justen schrieb:
>>
>>> I thought this might be a case where deviation from real hardware
>>> emulation could better serve the VM's needs.
>>>
>> If we have to write the code anyway, and if it can work just fine with
>> current KVM/Qemu, is there a reason not to use the same interface as
>> real hardware?
>>
> If there was a real device emulated by qemu, I would gladly make use
> of it in OVMF.
>
Nice. So should I dig up my flash emulator code and check which chips
are supported? Porting the code to Qemu shouldn't be too hard.
> I just thought this proposal would be much easier to implement, and
> not be restricted to any particular size. (Since -bios currently
> supports any size that is a multiple of 64kb.) A real device is going
> to imply a certain size.
>
Right, the constant size argument is definitely a point we need to talk
about.
We could sidestep the issue by always using a 16 MByte flash device
which gets filled from the top with the firmware image, but I'm not sure
if that has other side effects.
Another way to solve this would be to emulate multiple flash chips, one
per power-of-two size between 128 kB and 16 MB. Some SPI flash chip
families encode the size into their ID, so determining the size
algorithmically is as simple as calculating
1 << idbyte3
and emulating this is equally simple.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2011-03-10 22:30 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 4:51 [Qemu-devel] RFC: emulation of system flash Jordan Justen
2011-03-10 9:10 ` [Qemu-devel] " Avi Kivity
2011-03-10 18:43 ` Jordan Justen
2011-03-10 21:52 ` Carl-Daniel Hailfinger
2011-03-10 22:14 ` Jordan Justen
2011-03-10 22:31 ` Carl-Daniel Hailfinger [this message]
2011-03-10 22:58 ` Jordan Justen
2011-03-10 23:41 ` Carl-Daniel Hailfinger
2011-03-11 2:12 ` Jordan Justen
2011-03-10 9:47 ` Gleb Natapov
2011-03-10 11:27 ` Jan Kiszka
2011-03-10 11:46 ` Jan Kiszka
2011-03-10 11:53 ` Paolo Bonzini
2011-03-10 12:07 ` Jan Kiszka
2011-03-10 19:03 ` Jordan Justen
2011-03-10 19:23 ` Anthony Liguori
2011-03-10 20:05 ` Jordan Justen
2011-03-10 11:48 ` Gleb Natapov
2011-03-10 12:06 ` Jan Kiszka
2011-03-10 12:17 ` Gleb Natapov
2011-03-10 12:27 ` Jan Kiszka
2011-03-10 19:08 ` Jordan Justen
2011-03-10 19:13 ` Gleb Natapov
2011-03-10 21:46 ` Carl-Daniel Hailfinger
2011-03-10 22:11 ` Scott Wood
2011-03-10 21:41 ` Carl-Daniel Hailfinger
2011-03-10 22:05 ` Jordan Justen
2011-03-10 18:59 ` Jordan Justen
2011-03-10 19:12 ` Gleb Natapov
2011-03-10 19:50 ` Jordan Justen
2011-03-10 20:08 ` Антон Кочков
2011-03-10 20:21 ` Gleb Natapov
2011-03-11 21:41 ` Jordan Justen
2011-03-14 14:29 ` Gleb Natapov
2011-03-10 21:37 ` [Qemu-devel] " Carl-Daniel Hailfinger
2011-03-10 21:55 ` Jordan Justen
2011-03-10 22:10 ` Carl-Daniel Hailfinger
2011-03-10 22:29 ` Jordan Justen
2011-03-10 23:53 ` Carl-Daniel Hailfinger
2011-03-11 0:19 ` [Qemu-devel] " Jan Kiszka
2011-03-11 0:27 ` Carl-Daniel Hailfinger
2011-03-11 19:09 ` Jordan Justen
2011-03-11 23:10 ` Michal Suchanek
2011-03-12 9:24 ` Jan Kiszka
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=4D79513F.2090008@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=hramrach@centrum.cz \
--cc=jljusten@gmail.com \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).