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] XEN_HYPER_ITC_D and XEN_HYPER_ITC_I in vhpt_miss

To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, "Dietmar Hahn" <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] XEN_HYPER_ITC_D and XEN_HYPER_ITC_I in vhpt_miss
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Wed, 24 May 2006 12:07:45 +0800
Delivery-date: Tue, 23 May 2006 21:07:59 -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: AcZ+dDvy67gjGKXrTdK0lsPemrTY0AAATDAgABxbU9A=
Thread-topic: [Xen-ia64-devel] XEN_HYPER_ITC_D and XEN_HYPER_ITC_I in vhpt_miss
>From: Magenheimer, Dan (HP Labs Fort Collins)
>Sent: 2006年5月23日 22:40
>> > > > May it be that XEN_HYPER_ITC_D and XEN_HYPER_ITC_I are
>in
>> > >
>> > > the reverse
>> > >
>> > > > order?
>> > >
>> > > Good catch.
>> > >
>> > > Feel free to send a patch.
>> >
>> > Does this code ever get executed?  The VHPT is pinned by
>> > a TR, correct?
>
>Oops, Xen's VHPT is pinned, the guest's isn't pinned.
>
>> For sure it is strange we never hit this bug ;-)
>
>Yes, it looks like the faulty code should get executed.
>Maybe it quickly
>fixes itself because the wrong vtlb gets inserted,
>then another miss immediately occurs which is not
>a VHPT fault so the correct vtlb gets inserted.

Definitely. The key point is that vhpt entry is inserted after above bogus 
place and then TLB miss immediately happens after resuming with 
hardware triggered to walk vhpt table by inserting desired mapping. 
Above two insertions are only optimization code which don't hurt 
anything even not being there.

>
>Anyway, yes, please submit a patch!
>
>Dan
>

Yes, patch is needed.

Thanks,
Kevin

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