From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Subject: Re: [Qemu-devel] Modeling x86 early initialization accurately
Date: Wed, 26 Nov 2008 11:37:55 +0000 [thread overview]
Message-ID: <200811261137.56040.paul@codesourcery.com> (raw)
In-Reply-To: <492C80BF.4010103@gmx.net>
> - Start up with all RAM being readonly. Writes should be discarded,
> reads will usually return 0xff or be undefined. The "undefined" variant
> would allow the code to allocate RAM once and just switch write access
> on/off.
Does anything actually rely on this behavior?
I can see the need to the other bits, but it seems kinda strange that anything
would rely on RAM being readonly. This seems more like a coreboot bug than
anything else.
Paul
next prev parent reply other threads:[~2008-11-26 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 22:48 [Qemu-devel] Modeling x86 early initialization accurately Carl-Daniel Hailfinger
2008-11-26 2:04 ` Anthony Liguori
2008-11-26 3:26 ` Carl-Daniel Hailfinger
2008-11-26 16:36 ` Avi Kivity
2008-11-27 2:05 ` Carl-Daniel Hailfinger
2008-11-27 13:28 ` Avi Kivity
2008-11-27 14:22 ` Carl-Daniel Hailfinger
2008-11-26 11:37 ` Paul Brook [this message]
2008-11-26 13:29 ` Carl-Daniel Hailfinger
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=200811261137.56040.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=c-d.hailfinger.devel.2006@gmx.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).