[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] Question about vmx_ivt.S


  • To: "Tristan Gingold" <tgingold@xxxxxxx>, "Xen-ia64-devel" <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Tue, 9 Oct 2007 10:36:06 +0800
  • Delivery-date: Mon, 08 Oct 2007 19:36:38 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcgDdYqZeiNcbBuDRSq/eJfNnwHypQGpUcCg
  • Thread-topic: [Xen-ia64-devel] Question about vmx_ivt.S

Hi Tristan,

Yes the mf is necessary,
Hardware can speculatively load vhpt entries from VTHP page.
We had spent a lot of effort to identity this issue.

Anthony






>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-ia64-devel-
>bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tristan Gingold
>Sent: 2007年9月30日 23:26
>To: Xen-ia64-devel
>Subject: [Xen-ia64-devel] Question about vmx_ivt.S
>
>Hi,
>
>for both itlb and dtlb handlers, while swapping first and found entries:
>    st8 [r16] = r29, VLE_ITIR_OFFSET - VLE_TITAG_OFFSET
>    st8 [r28] = r22, VLE_ITIR_OFFSET - VLE_TITAG_OFFSET
>    extr.u r19 = r27, 56, 4
>    mf
>    ;;
>    ld8 r29 = [r16]
>    ld8 r22 = [r28]
>    dep r27 = r0, r27, 56, 4
>    dep r25 = r19, r25, 56, 4
>
>Is the mf (memory fence) necessary ?  The VHPT is per-cpu.
>
>Tristan.
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.