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:00:54 -0700
Cc: "Xu, James" <james.xu@xxxxxxxxx>, "Wang, Shane" <shane.wang@xxxxxxxxx>, "Wei, Gang" <gang.wei@xxxxxxxxx>
Delivery-date: Mon, 29 Oct 2007 11:03:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C34BCE40.1798F%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: <D936D925018D154694D8A362EEB0892002C7C389@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C34BCE40.1798F%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgYPKeHAh+s/rrjQ0OzxTZHSH6adQB0Zgj0AAzUsnAAA3v0QgAAvpSgAAB6yw4AAD/usA==
Thread-topic: [Xen-devel] [PATCH] Intel(R) Trusted Execution Technology support
On Monday, October 29, 2007 10:52 AM, Keir Fraser wrote:
> On 29/10/07 17:41, "Cihula, Joseph" <joseph.cihula@xxxxxxxxx> wrote:
> 
>>> Why is the memory region not marked as E820_UNUSABLE by tboot?
And/or extend
>>> the multiboot info structure and transmit the address of the shared
page
>>> that way.
>> 
>> I didn't mark it as UNUSABLE because dom0 doesn't like low memory
that
>> it can't probe and I didn't realize that there would be a problem
with
>> marking it RESERVED.  However, I can mark it as UNUSABLE and then
when I
>> find it, change it to RESERVED.  I'll send a patch for this as well.
> 
> 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.

Joe

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

<Prev in Thread] Current Thread [Next in Thread>