public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Avi Kivity <avi@qumranet.com>
Cc: Matt_Domsch@Dell.com, pjones@redhat.com, kvm@vger.kernel.org,
	Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: qemu oddness with isolinux vesamenu.c32
Date: Mon, 21 Jul 2008 05:51:06 -0700	[thread overview]
Message-ID: <4884863A.2030609@zytor.com> (raw)
In-Reply-To: <48845A2C.4050306@qumranet.com>

Avi Kivity wrote:
> H. Peter Anvin wrote:
>> H. Peter Anvin wrote:
>>>
>>> Yes, although simulating the memory "pre-shadowed" works just as 
>>> well; then it should be marked readonly by the BIOS immediately prior 
>>> to running INT 19h.
>>
>> On top of this, getting proper DDIM support and PCI expansion ROM into 
>> the BIOS would be a good thing.  A PCI expansion ROM is attached to a 
>> PCI device as a BAR and mapped into high memory, it is then copied to 
>> shadowed RAM by the BIOS and its initialization stub is run.  This is 
>> done one device at a time, so that the initialization code can be 
>> discarded, per the DDIM spec.
> 
> I imagine it's necessary for proper pci device assignment.
> 

Well, if nothing else it would permit PCI device ROMs to work 
unmodified.  I was rather disappointed when I found out I couldn't 
simulate PXE ROMs, even from devices which we can emulate.

	-hpa

      reply	other threads:[~2008-07-21 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E9909A75A543064DB66E55B8E3BE41EC72701C@ausx3mps307.aus.amer.dell.com>
     [not found] ` <48800A9D.1080403@zytor.com>
2008-07-18 16:25   ` qemu oddness with isolinux vesamenu.c32 H. Peter Anvin
2008-07-18 16:53     ` H. Peter Anvin
2008-07-19  7:37     ` Avi Kivity
2008-07-19 18:29       ` H. Peter Anvin
2008-07-20  1:45         ` H. Peter Anvin
2008-07-21  9:43           ` Avi Kivity
2008-07-21 12:51             ` H. Peter Anvin [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=4884863A.2030609@zytor.com \
    --to=hpa@zytor.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=kvm@vger.kernel.org \
    --cc=pjones@redhat.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