From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: guest attempted write to read-only memory page.
Date: Thu, 25 Dec 2008 17:36:07 +0900 [thread overview]
Message-ID: <495345F7.6080905@jp.fujitsu.com> (raw)
In-Reply-To: <C578F054.208DC%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 25/12/2008 01:54, "Akio Takebe" <takebe_akio@jp.fujitsu.com> wrote:
>
>>> I make a quick test, that warning disappears after moving disable
>>> action post rom_scan. But I haven't found the place triggering such
>>> write violation, as in previous revision write access is also disabled
>>> before rom_scan. It could come from recent bochs update on
>>> expansion rom part by 18931.
>> Sorry for my late response.
>> That's a bug of mine.
>>
>> Some option ROMs would do write accesses.
>> So rombios need to enable write acess before rom_scan.
>> I'll post a patch to fix.
>
> This behaviour existed before your upgrade, and it's not a bug. I fixed by
> removing the warning message.
>
But shadow memory should enable write accesses during INIT and BCV.
It's in BBS spec.
Best Regards,
Akio Takebe
next prev parent reply other threads:[~2008-12-25 8:36 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
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 [this message]
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=495345F7.6080905@jp.fujitsu.com \
--to=takebe_akio@jp.fujitsu.com \
--cc=keir.fraser@eu.citrix.com \
--cc=kevin.tian@intel.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.