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

[Xense-devel] Re: [Xen-devel] [PATCH] Intel(R) Trusted Execution Technol

To: "Cihula, Joseph" <joseph.cihula@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>, <xense-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xense-devel] Re: [Xen-devel] [PATCH] Intel(R) Trusted Execution Technology support
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 29 Oct 2007 17:52:00 +0000
Cc: "Xu, James" <james.xu@xxxxxxxxx>, "Wang, Shane" <shane.wang@xxxxxxxxx>, "Wei, Gang" <gang.wei@xxxxxxxxx>
Delivery-date: Mon, 29 Oct 2007 10:52:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D936D925018D154694D8A362EEB0892002C7C389@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xense-devel-request@lists.xensource.com?subject=help>
List-id: "A discussion list for those developing security enhancements for Xen." <xense-devel.lists.xensource.com>
List-post: <mailto:xense-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xense-devel>, <mailto:xense-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xense-devel>, <mailto:xense-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xense-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgYPKeHAh+s/rrjQ0OzxTZHSH6adQB0Zgj0AAzUsnAAA3v0QgAAvpSgAAB6yw4=
Thread-topic: [Xen-devel] [PATCH] Intel(R) Trusted Execution Technology support
User-agent: Microsoft-Entourage/11.3.6.070618
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)?

 -- Keir



_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel

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