From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MtOU3-0004w4-Kt for qemu-devel@nongnu.org; Thu, 01 Oct 2009 12:26:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MtOTz-0004rB-W4 for qemu-devel@nongnu.org; Thu, 01 Oct 2009 12:26:23 -0400 Received: from [199.232.76.173] (port=36465 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MtOTz-0004qx-Ol for qemu-devel@nongnu.org; Thu, 01 Oct 2009 12:26:19 -0400 Received: from mail-bw0-f211.google.com ([209.85.218.211]:56191) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MtOTz-0008Jz-Js for qemu-devel@nongnu.org; Thu, 01 Oct 2009 12:26:19 -0400 Received: by bwz7 with SMTP id 7so276427bwz.34 for ; Thu, 01 Oct 2009 09:26:18 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4AC4725D.1020009@redhat.com> References: <1254325401-18777-1-git-send-email-kraxel@redhat.com> <4AC4725D.1020009@redhat.com> From: Blue Swirl Date: Thu, 1 Oct 2009 19:25:58 +0300 Message-ID: Subject: Re: [Qemu-devel] [PATCH] Reorganize option rom (+linux kernel) loading. Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: qemu-devel@nongnu.org On Thu, Oct 1, 2009 at 12:11 PM, Gerd Hoffmann wrote: > =C2=A0Hi, > >> 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? =C2=A0Works for me. =C2=A0Details please. =C2=A0sparc 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. =C2=A0So in that case writing roms = on reset > isn't very useful because the guest shouldn't be able to modify them in t= he > first place. =C2=A0It doesn't harm though, except that we keep a copy of = the roms > around for no reason. =C2=A0Maybe make restore-on-reset opt-in? Or make writability opt-in feature?