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-ia64-devel

RE: [Xen-ia64-devel] PATCH: cleanup of tlbflush

To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>, "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, "Alex Williamson" <alex.williamson@xxxxxx>, "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] PATCH: cleanup of tlbflush
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Wed, 10 May 2006 20:37:02 +0800
Delivery-date: Wed, 10 May 2006 05:37:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZ0KFqCeh6lzcsfQVyf0dzb+n6LOQABbFgg
Thread-topic: [Xen-ia64-devel] PATCH: cleanup of tlbflush
>From: Tristan Gingold [mailto:Tristan.Gingold@xxxxxxxx]
>Sent: 2006年5月10日 19:57
>
>Le Mercredi 10 Mai 2006 13:38, Tian, Kevin a écrit :
>> From: Tristan Gingold [mailto:Tristan.Gingold@xxxxxxxx]
>>
>> >Sent: 2006年5月10日 18:47
>> >
>> >> I see your concern about flush efficiency. However we still need set
>> >> necessary mask bits for correctness, right?
>> >
>> >Not yet, because pages are not transfered.
>>
>> It's not specific to page flipping. Simple page sharing also has same
>> problem.
>No really.  Page sharing is only from domU to dom0.  Thus, if we trust
>dom0 we
>don't need to flush all the tlb.

No, even for dom0, the mapped va may be accessed on several vcpus 
and thus you have to flush all related TLBs. On this point, there's no 
need to differentiate dom0 or domU. Simple thing is to flush based on 
domain_dirty_cpumask upon unmap request.

Thanks,
Kevin

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