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

RE: [Xen-ia64-devel] vPAL VTi incorrect values


  • To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Fri, 14 Apr 2006 21:44:09 +0800
  • Delivery-date: Fri, 14 Apr 2006 06:44:26 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZfyAD8NYBwX4GiRJawy6yxnX911QAAOtSA
  • Thread-topic: [Xen-ia64-devel] vPAL VTi incorrect values

>From: Tristan Gingold
>Sent: 2006?4?14? 21:37
>To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: [Xen-ia64-devel] vPAL VTi incorrect values
>
>Hi,
>
>within XenVTi, cat /proc/pal/cpu0/vm_info gives:
># cat /proc/pal/cpu0/vm_info
>Physical Address Space         : 50 bits
>Virtual Address Space          : 61 bits
>Protection Key Registers(PKR)  : 16
>Implemented bits in PKR.key    : 24
>Hash Tag ID                    : 0x2
>Size of RR.rid                 : 24
>Supported memory attributes    : WB, UC, UCE, WC, NaTPage
>
>RR.rid and virtual address space are wrong!
>
>RR.rid may be a real problem given the previous patch which now check rid.
>

Good catch!

Some pal emulations are implemented within guest firmware.
Virtual address space should be implemented within guest firmware,
Because it's always 60.(there are 61 bits virtual address on Montecito).
Rid bits should be emulated by VMM.


>I don't know how to fix that because these values don't come from pal_emul.c.
>I suppose they come from the virtual bios.
>
>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®.