qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Антон Кочков" <anton.kochkov@gmail.com>
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:08:51 +0300	[thread overview]
Message-ID: <AANLkTin4soHT==SDhT376gort9_f9K=zpgEOczPC0Usa@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=nE-YwEvdmCVHcAjc_RX0XfN9PMOk89i8o6i46@mail.gmail.com>

As I'm working on bootrom loading support for omap/arm platform, I'm
have suggestion about something more universal than -bios (and even
-flash) option. Because Flash can be NOR, can be NAND, but on-chip
memory is not flash memory. So may be something like -rom option?

Best regards,
Anton Kochkov.




On Thu, Mar 10, 2011 at 22:50, Jordan Justen <jljusten@gmail.com> wrote:
> On Thu, Mar 10, 2011 at 11:12, Gleb Natapov <gleb@redhat.com> wrote:
>> On Thu, Mar 10, 2011 at 10:59:07AM -0800, Jordan Justen wrote:
>>> Yes, this definitely could add firmware upgrade issues, but I thought
>>> this could be the responsibility of the firmware itself.  For example,
>>> OVMF could have an outside of VM tool to merge new releases, or it
>>> could have an inside of VM firmware update process.
>> Why require another tool if can do without? I don't see any advantages
>> in storing firmware code and its non-volatile storage in the same image,
>> but I do see disadvantages.
>
> I agree.  The implications of a firmware image getting out of sync
> with qemu were a bit of a concern to me.  But, having both -bios +
> -flash just below -bios was starting to seem a bit complicated.
>
> And, I guess as a firmware developer, I thought it might be
> interesting to consider enabling a firmware update process within the
> VM. :)
>
> How about?
> 1) Pure rom:
> -bios bios.bin
> 2) Rom + flash below rom:
> -bios bios.bin,flash=flash.bin
> 3) Pure flash:
> -bios flash=flash.bin
>
> Or, with a separate new -flash option:
> 1) Pure rom:
> -bios bios.bin
> or no -bios or -flash parameters
> 2) Rom + flash below rom:
> -bios bios.bin -flash flash.bin
> 3) Pure flash:
> -flash flash.bin
>
>> It is not even about performance (which will be very bad for 1MB). KVM
>> can't run code from MMIO region, so the part that contains firmware
>> has to be memory.
>
> Hmm.  That's good to know. :)
>
> So, perhaps this feature should build upon the other feature you and
> Jan are discussing.  When will it become available?
>
> Thanks,
>
> -Jordan
>
>

  reply	other threads:[~2011-03-10 20:08 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
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         ` Антон Кочков [this message]
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='AANLkTin4soHT==SDhT376gort9_f9K=zpgEOczPC0Usa@mail.gmail.com' \
    --to=anton.kochkov@gmail.com \
    --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).