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] Re: [Patch] the interface of invalidating qemu mapcache

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Li, Xin B" <xin.b.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Re: [Patch] the interface of invalidating qemu mapcache
From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Date: Sat, 27 Jan 2007 18:29:45 +0800
Delivery-date: Sat, 27 Jan 2007 02:29:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1E0C5BF.7E69%Keir.Fraser@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbhNpSgnLlsyleeR3aZurd/xO5mYAAmjw1QAHpYsZANUy+bAAbmp7kgAzBSt0AAA6R4dgADlbrAAByKhhoAAgYC0A==
Thread-topic: [Xen-devel] Re: [Patch] the interface of invalidating qemu mapcache
Keir,
Attached is the updated version. The exported qemu_invalidate_map_cache() just 
blows the entire qemu mapcache.
Would you please give some comments? Thanks a lot!

 -- Dexuan
Signed-off-by: Dexuan Cui <dexuan.cui@xxxxxxxxx>

>-----Original Message-----
>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2007年1月27日 17:03
>To: Li, Xin B; Cui, Dexuan; xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] Re: [Patch] the interface of invalidating qemu 
>mapcache
>
>On 26/1/07 7:33 pm, "Li, Xin B" <xin.b.li@xxxxxxxxx> wrote:
>
>> Yes, it's much simpler if we just blow the entire mapcache each time we
>> release memory to Xen or get some back from Xen.
>
>For populating memory, qemu should probably refill the mapcache on demand.
>It ought to be catching page faults on access to the mapcache anyway (easy,
>just need a SIGSEGV handler). If it detects a mapcache access it should
>first attempt to refill that mapcache entry and if that fails then do
>something appropriate (crash the domain?).
>
> -- Keir

Attachment: interface_of_invalidating_qemu_mapcache-2.diff
Description: interface_of_invalidating_qemu_mapcache-2.diff

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