From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: 'Akio Takebe' <takebe_akio@jp.fujitsu.com>
Subject: Re: guest attempted write to read-only memory page.
Date: Mon, 22 Dec 2008 10:33:03 +0000 [thread overview]
Message-ID: <C5751D5F.207C2%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <0A882F4D99BBF6449D58E61AAFD7EDD603BB49CB@pdsmsx502.ccr.corp.intel.com>
On 22/12/2008 10:12, "Tian, Kevin" <kevin.tian@intel.com> wrote:
> I guess it's caused by 18931 to update rombios to latest bochs
> version, and some writes to rom area are added outside of disabling
> rom write access. But I'm not familiar with this part, and thus hope
> others (Akio?) may take a deeper dive.
Etherboot likes to try to write to its ROM area. That's why I actually
silenced the warning in __hvm_copy(). I would guess the reason you see this
issue now is because the accesses are taking the shadow-fault path, which
means you are no longer emulating real mode? ;-)
Possibly we should silence the shadow code too, at least perhaps while in
real mode or for a certain EIP range.
-- Keir
next prev parent reply other threads:[~2008-12-22 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 10:12 guest attempted write to read-only memory page Tian, Kevin
2008-12-22 10:33 ` Keir Fraser [this message]
2008-12-22 13:11 ` Tian, Kevin
2008-12-22 13:20 ` Tian, Kevin
2008-12-22 13:42 ` Keir Fraser
2008-12-22 14:21 ` Tian, Kevin
2008-12-22 15:11 ` Keir Fraser
2008-12-23 2:37 ` Tian, Kevin
2008-12-25 1:54 ` Akio Takebe
2008-12-25 8:09 ` Keir Fraser
2008-12-25 8:36 ` Akio Takebe
2008-12-25 9:09 ` Keir Fraser
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=C5751D5F.207C2%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=kevin.tian@intel.com \
--cc=takebe_akio@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.