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