WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] guest attempted write to read-only memory page.

To: 'Keir Fraser' <keir.fraser@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] guest attempted write to read-only memory page.
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Tue, 23 Dec 2008 10:37:54 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: 'Akio Takebe' <takebe_akio@xxxxxxxxxxxxxx>
Delivery-date: Mon, 22 Dec 2008 18:38:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5755E9F.207E7%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <0A882F4D99BBF6449D58E61AAFD7EDD603BB49D0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C5755E9F.207E7%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclkHdhNymC5crU+TeGYz4yjUsNejgAAtLZCAAVBrFAAAHy2QAAA4MYTAAE945AAAdwMjAAX832Q
Thread-topic: [Xen-devel] guest attempted write to read-only memory page.
>From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx] 
>Sent: Monday, December 22, 2008 11:11 PM
>
>On 22/12/2008 14:21, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:
>
>>> Yes, I can repro the warnings. They are due to the vm86 acceleration
>>> changes. 
>>> 
>> 
>> I saw you removed the warning in latest tree, but sorry that 
>I'm still
>> a bit confused about logic here. Could you help clarify the 
>underlying
>> story to me? :-) Why is such write attempt legitimate? Is 
>the emulation
>> a dummy nop or actually emulated?
>
>The write is thrown away, and the instruction is skipped. Etherboot can
>handle these write attempts failing (obviously, since it could 
>really be
>executed out of ROM). It attempts them just to set up some version info
>strings, I think -- nothing at all important.
>

ok, got it.

Thanks,
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel