From: "Sebastian Herbszt" <herbszt@gmx.de>
To: Gleb Natapov <gleb@redhat.com>, Kevin O'Connor <kevin@koconnor.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: POST failure (loop) with isapc and seabios
Date: Mon, 23 Nov 2009 18:57:47 +0100 [thread overview]
Message-ID: <17CE86C19414401F869FD85A63BF1250@FSCPC> (raw)
In-Reply-To: <20091123111601.GH2999@redhat.com>
Gleb Natapov wrote:
> On Sun, Nov 22, 2009 at 10:38:42AM -0500, Kevin O'Connor wrote:
>> On Sun, Nov 22, 2009 at 05:10:53PM +0200, Gleb Natapov wrote:
>> > On Sun, Nov 22, 2009 at 04:07:56PM +0100, Sebastian Herbszt wrote:
>> > > Gleb Natapov wrote:
>> > > >May be make qemu to map it writable if isapc is specified.
>> > >
>> > > I don't think keeping the segment writable after POST is a good idea.
>> > >
>> > Isn't it writable now after POST with pcipc? Why this is not a good
>> > idea?
>>
>> SeaBIOS and bochs bios will make the f-segment readonly at the end of
>> post. See make_bios_readonly() in src/shadow.c.
>>
> I see SeaBIOS does this, but I don't see where bochs bios does this.
bios_lock_shadow_ram() in rombio32.c.
- Sebastian
next prev parent reply other threads:[~2009-11-23 18:01 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 21:30 [Qemu-devel] POST failure (loop) with isapc and seabios Sebastian Herbszt
2009-11-20 22:51 ` [Qemu-devel] " Kevin O'Connor
2009-11-21 14:37 ` Sebastian Herbszt
2009-11-22 12:35 ` Gleb Natapov
2009-11-22 15:07 ` Sebastian Herbszt
2009-11-22 15:10 ` Gleb Natapov
2009-11-22 15:31 ` Sebastian Herbszt
2009-11-22 15:38 ` Gleb Natapov
2009-11-22 17:40 ` Kevin O'Connor
2009-11-22 21:15 ` Sebastian Herbszt
2009-11-22 22:04 ` Sebastian Herbszt
2009-11-23 11:14 ` Gleb Natapov
2009-11-23 11:17 ` Gleb Natapov
2009-11-22 20:01 ` Sebastian Herbszt
2009-11-23 11:11 ` Gleb Natapov
2009-11-23 19:19 ` Sebastian Herbszt
2009-11-23 19:43 ` Gleb Natapov
2009-11-23 21:30 ` Sebastian Herbszt
2009-11-24 6:28 ` Gleb Natapov
2009-11-24 14:38 ` Jamie Lokier
2009-11-24 14:40 ` Gleb Natapov
2009-11-25 6:09 ` Jamie Lokier
2009-11-25 12:20 ` Gleb Natapov
2009-11-25 15:31 ` Kevin O'Connor
2009-11-25 16:42 ` Gleb Natapov
2009-11-25 22:11 ` Sebastian Herbszt
2009-11-27 3:00 ` Jamie Lokier
2009-11-27 19:13 ` Sebastian Herbszt
2009-11-25 22:04 ` Sebastian Herbszt
2009-11-25 22:53 ` Kevin O'Connor
2009-11-26 6:49 ` Gleb Natapov
2009-11-26 7:15 ` Kevin O'Connor
2009-11-26 7:20 ` Gleb Natapov
2009-11-26 7:48 ` Kevin O'Connor
2009-11-26 7:56 ` Gleb Natapov
2009-11-26 8:12 ` Kevin O'Connor
2009-11-26 8:19 ` Gleb Natapov
2009-11-26 16:03 ` Kevin O'Connor
2009-11-26 22:35 ` Sebastian Herbszt
2009-11-27 5:39 ` Kevin O'Connor
2009-11-26 6:45 ` Gleb Natapov
2009-11-26 20:55 ` Sebastian Herbszt
2009-11-27 7:44 ` Gleb Natapov
2009-11-27 20:42 ` Sebastian Herbszt
2009-11-29 8:20 ` Gleb Natapov
2009-11-29 22:53 ` Natalia Portillo
2009-11-30 7:12 ` Gleb Natapov
2009-11-30 20:53 ` Jamie Lokier
2009-11-30 21:02 ` Natalia Portillo
2009-12-01 2:16 ` Kevin O'Connor
2009-11-30 20:34 ` Sebastian Herbszt
2009-12-01 9:37 ` Gleb Natapov
2009-11-25 21:08 ` Sebastian Herbszt
2009-11-24 23:27 ` Sebastian Herbszt
2009-11-25 10:48 ` Gleb Natapov
2009-11-22 15:38 ` Kevin O'Connor
2009-11-23 11:16 ` Gleb Natapov
2009-11-23 17:57 ` Sebastian Herbszt [this message]
2009-11-23 18:07 ` Gleb Natapov
2009-11-23 19:12 ` Sebastian Herbszt
2009-11-23 19:18 ` 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=17CE86C19414401F869FD85A63BF1250@FSCPC \
--to=herbszt@gmx.de \
--cc=gleb@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).