Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xense-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 10:41:12 -0700
Cc: "Xu, James" <james.xu@xxxxxxxxx>, "Wang, Shane" <shane.wang@xxxxxxxxx>, "Wei, Gang" <gang.wei@xxxxxxxxx>
Delivery-date: Mon, 29 Oct 2007 10:44:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C34BC609.17952%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: <D936D925018D154694D8A362EEB0892002C7C0AD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C34BC609.17952%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgYPKeHAh+s/rrjQ0OzxTZHSH6adQB0Zgj0AAzUsnAAA3v0QgAAvpSg
Thread-topic: [Xen-devel] [PATCH] Intel(R) Trusted Execution Technology support
On Monday, October 29, 2007 10:17 AM, Keir Fraser wrote:
> On 29/10/07 15:38, "Cihula, Joseph" <joseph.cihula@xxxxxxxxx> wrote:
> 
>>>> Attached is a patch that adds Intel(R) Trusted Execution Technology
>>>> (Intel(R) TXT) support to Xen.  Intel(R) TXT was formerly known by
the
>>>> codename LaGrande Technology (LT).
>>> 
>>> Seems to be missing asm-x86/tboot.h.
>> 
>> The build for tboot/tboot copies this file from tboot/include to
>> xen/include/asm-x86.  Do you prefer that it get checked in to Xen's
repo
>> instead?
> 
> Okay, another issue. You can't probe for tboot by mapping and reading
every
> E820_RESERVED region (which is what the code you add to x86/setup.c
does).
> You don't know what mmio regions you could be conflicting with by
making a
> cacheable mapping and issuing memory reads (which can have side
effects when
> issued to I/O devices).
> 
> 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.

> 
>  -- Keir

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

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