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

[Xen-ia64-devel] Uncached offset: Region 6 -> lower half of VTi-reserved VM space


  • To: <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Mon, 13 Jun 2005 14:35:54 -0700
  • Delivery-date: Mon, 13 Jun 2005 21:35:51 +0000
  • List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcVwX+CR8RimBlWdTgqhrwBuwdjrAA==
  • Thread-topic: Uncached offset: Region 6 -> lower half of VTi-reserved VM space

I've just pushed a patch to xeno-unstable-ia64.bk which finishes
the virtual address changes submitted by Intel (Kevin, I think)
some months ago, where the Xen-reserved VA space was changed from
        0xf000000000000000-0xf7ffffffffffffff
                to
        0xe800000000000000-0xf7ffffffffffffff
to correspond to one less bit in the guest's virtual address
space.

The "uncached" portion of Xen's virtual address space was
still mapped at 0xd000000000000000.  I have moved it
to 0xe800000000000000 to properly correspond with the
one-less-bit-guest-VA space.

A couple of changes were required in ivt.S so corresponding
changes need to be made in vmx_ivt.S.  The only other change
was the constant value in io.h (a patched file) for
__IA64_UNCACHED_OFFSET.

Note that I also cleaned up a test to ensure that guest
data accesses are properly checked against the legal
address range.  (Not a problem on VTI as these addresses
could never be generated.)

See changeset 1.1711.  If someone at Intel could submit
the corresponding vmx_ivt.S change, I would appreciate it.

Thanks,
Dan

_______________________________________________
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®.