From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Gleb Natapov <gleb@redhat.com>, Alexander Graf <agraf@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Kevin O'Connor <kevin@koconnor.net>, beth kon <eak@us.ibm.com>
Subject: Re: [Qemu-devel] PC machine types switched to SeaBIOS/gPXE
Date: Tue, 10 Nov 2009 15:02:15 +0200 [thread overview]
Message-ID: <4AF96457.1070701@redhat.com> (raw)
In-Reply-To: <20091109184157.GA12566@mothafucka.localdomain>
On 11/09/2009 08:41 PM, Glauber Costa wrote:
>
>> pc.c:
>>
>> } else {
>> /* High and recent kernel */
>> real_addr = 0x10000;
>> cmdline_addr = 0x20000;
>> prot_addr = 0x100000;
>> }
>>
>> If I'm not totally mistaken, 0x10000 is< 1MB :-).
>>
>> So yes, I think there should be a fw-conf interface that tells qemu to
>> reload all volatile option rom regions (which it keeps track of for
>> reset anyway). We just need to make sure it doesn't overwrite the BIOS
>> itself, as data in there might have been changed already.
>>
> Can't we put these data somewhere else, and let our int19 handler copy
> it to the right location?
>
Anywhere you put it the bios has a right to trample. Of course our bios
(and its maintainer) are cooperative, but there's not reason to impose
on that if we can do the right thing and load the data at the right moment.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-11-10 13:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 14:54 [Qemu-devel] PC machine types switched to SeaBIOS/gPXE Anthony Liguori
2009-10-30 19:37 ` [Qemu-devel] " Jan Kiszka
2009-10-30 19:45 ` Anthony Liguori
2009-10-31 12:42 ` Stefan Weil
2009-10-31 13:10 ` Jan Kiszka
2009-11-02 23:09 ` Beth Kon
2009-11-02 23:22 ` Anthony Liguori
2009-11-03 4:16 ` Kevin O'Connor
2009-11-03 14:11 ` Beth Kon
2009-11-04 1:38 ` Kevin O'Connor
2009-11-04 1:55 ` Anthony Liguori
2009-10-31 11:07 ` [Qemu-devel] " Stefan Weil
2009-10-31 12:02 ` [Qemu-devel] " Jan Kiszka
2009-11-02 12:51 ` [Qemu-devel] " Alexander Graf
2009-11-02 13:08 ` Avi Kivity
2009-11-02 13:15 ` Alexander Graf
2009-11-02 13:32 ` Avi Kivity
2009-11-02 13:51 ` Kevin O'Connor
2009-11-02 13:56 ` Avi Kivity
2009-11-02 14:06 ` Alexander Graf
2009-11-02 14:39 ` Avi Kivity
2009-11-09 18:41 ` Glauber Costa
2009-11-10 13:02 ` Avi Kivity [this message]
2009-11-10 13:03 ` Alexander Graf
2009-11-10 13:07 ` Avi Kivity
2009-11-10 13:09 ` Alexander Graf
2009-11-03 4:50 ` Kevin O'Connor
2009-11-03 4:57 ` Alexander Graf
2009-11-03 5:01 ` Avi Kivity
2009-11-03 6:02 ` Kevin O'Connor
2009-11-03 6:08 ` Avi Kivity
2009-11-03 13:42 ` Kevin O'Connor
2009-11-03 4:58 ` Avi Kivity
2009-11-02 14:51 ` Gleb Natapov
2009-11-02 14:54 ` Gleb Natapov
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=4AF96457.1070701@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=eak@us.ibm.com \
--cc=gleb@redhat.com \
--cc=glommer@redhat.com \
--cc=kevin@koconnor.net \
--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).