qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Reorganize option rom (+linux kernel) loading.
Date: Thu, 1 Oct 2009 19:25:58 +0300	[thread overview]
Message-ID: <f43fc5580910010925r7ed7e621yd926f68da824d37c@mail.gmail.com> (raw)
In-Reply-To: <4AC4725D.1020009@redhat.com>

On Thu, Oct 1, 2009 at 12:11 PM, Gerd Hoffmann <kraxel@redhat.com> wrote:
>  Hi,
>
>> Nice idea. The implementation seems to be buggy, I only ever see one
>> rom
>
> On !pc platforms only elf roms will show up.
>
>> and for example sparc-test crashes when issuing 'info roms'.
>
> Huh?  Works for me.  Details please.  sparc is one of the archs I've
> actually tested:

OK, V2 seems to work, except that the command line is not passed:
NET: Registered protocol family 1
NET: Registered protocol family 17
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
 <0>Press L1-A to return to the boot prom

>> Perhaps 'info roms' could also check whether the rom has been changed?
>
> Point being?

Could be useful information. Maybe not.

>> On most platforms roms are really read only memories.
>
> Yep, I've noticed on a quick glimpse.  So in that case writing roms on reset
> isn't very useful because the guest shouldn't be able to modify them in the
> first place.  It doesn't harm though, except that we keep a copy of the roms
> around for no reason.  Maybe make restore-on-reset opt-in?

Or make writability opt-in feature?

  reply	other threads:[~2009-10-01 16:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 15:43 [Qemu-devel] [PATCH] Reorganize option rom (+linux kernel) loading Gerd Hoffmann
     [not found] ` <m34oqkmf0n.fsf@neno.mitica>
2009-09-30 19:07   ` [Qemu-devel] " Gerd Hoffmann
2009-09-30 19:51 ` [Qemu-devel] " Blue Swirl
2009-10-01  9:11   ` Gerd Hoffmann
2009-10-01 16:25     ` Blue Swirl [this message]
2009-10-02 11:40       ` Gerd Hoffmann
2009-10-02 15:19         ` Gerd Hoffmann
2009-10-02 17:58           ` Blue Swirl
2009-10-06 21:18             ` Gerd Hoffmann
2009-10-02 17:56         ` Blue Swirl
  -- strict thread matches above, loose matches on Subject: below --
2009-10-01 14:42 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=f43fc5580910010925r7ed7e621yd926f68da824d37c@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=kraxel@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 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).