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] Intel(R) Trusted Execution Technology support

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>, <xense-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Intel(R) Trusted Execution Technology support
From: "Cihula, Joseph" <joseph.cihula@xxxxxxxxx>
Date: Mon, 29 Oct 2007 11:34:34 -0700
Cc: "Xu, James" <james.xu@xxxxxxxxx>, "Wang, Shane" <shane.wang@xxxxxxxxx>, "Wei, Gang" <gang.wei@xxxxxxxxx>
Delivery-date: Mon, 29 Oct 2007 11:40:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C34BD148.17997%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <D936D925018D154694D8A362EEB0892002C7C40F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C34BD148.17997%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgYPKeHAh+s/rrjQ0OzxTZHSH6adQB0Zgj0AAzUsnAAA3v0QgAAvpSgAAB6yw4AAD/usAAAM7T7AACBpTA=
Thread-topic: [Xen-devel] [PATCH] Intel(R) Trusted Execution Technology support
On Monday, October 29, 2007 11:05 AM, Keir Fraser wrote:
> On 29/10/07 18:00, "Cihula, Joseph" <joseph.cihula@xxxxxxxxx> wrote:
> 
>>> By low memory, do you mean the signature is in the bottom megabyte
of
>>> memory? If that's guaranteed then can we just scan the whole lot
>>> 0x00000-0xfffff (excluding VGA hole)?
>> 
>> Yes, it's in the lower 1MB and that is where dom0 has problems with
>> gaps.  But I think that the UNUSABLE->RESERVED approach will be just
as
>> effective and reduce the amount of memory to scan as well.
> 
> Okay, we should limit the scan to page-aligned addresses in UNUSABLE
regions
> below 1MB. It makes sense to put the UNUSABLE->RESERVED hack in Xen
itself,
> rather than in tboot. Once the interface is baked into 3.2.0 it's not
> changing on our side.

I'd like to allow for the shared page to be moved to a higher memory
location in the future, so I'd prefer not to limit the search to below
1MB.  Since only tboot is using the UNUSABLE type and it should find the
shared page in the first UNUSABLE section anyway (whether it gets moved
or not), the search should still be quick.  Also, I'll only change the
type from UNUSABLE->RESERVED if it is found in the lower 1MB.

Joe

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