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

Re: [Xen-devel] [PATCH] vmwrite high 32 bits of 64bit VMCS fields when i

To: "Li, Xin B" <xin.b.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] vmwrite high 32 bits of 64bit VMCS fields when in PAE mode
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Wed, 11 Jul 2007 07:59:24 +0100
Delivery-date: Tue, 10 Jul 2007 23:54:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <B30DA1341B0CFA4893EF8A36B40B5C5D015E6B19@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfDCkCwwQ9aXwykSueQB++MWscE/AAEXrFvAAi6ut0AEEzy4AACSlby
Thread-topic: [Xen-devel] [PATCH] vmwrite high 32 bits of 64bit VMCS fields when in PAE mode
User-agent: Microsoft-Entourage/11.3.3.061214
On 11/7/07 06:58, "Li, Xin B" <xin.b.li@xxxxxxxxx> wrote:

>> Oh, furthermore with a 32-bit build of Xen we have to be safe for the
> case
>> that VMX_BASIC_MSR[48]==1 (which Vol 3B Appendix G.1 says is true for
> non
>> Intel64 CPUs like Yonah). In this case the physical pointers poked into
> the
>> VMCS are limited to 32 bits. We may as well limit all such structures
> to
>> below 4GB in all cases with a 32-bit build of Xen.
>> 
> 
> So we need keep this mind for all data structures referenced by pointers
> in a VMCS when on 32bit Xen, or maybe how about add a memory allocation
> function wrapper for this purpose?

I think I fixed this now. Most of the structures were inside the Xen image
(io_bitmap) or were allocated from Xen heap (msr_bitmap, vmcs, apic_access).
The only exception was the apic_regs page -- I now restricted it to 32-bit
addresses on a 32-bit build of Xen if running on an Intel CPU.

Changeset 15526 in the staging tree.

 -- Keir


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