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/
Home Products Support Community News


Re: [Xen-devel] [RFC][PATCH][1/4] Intel(R) Trusted Execution Technology

To: "Cihula, Joseph" <joseph.cihula@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>, <xense-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC][PATCH][1/4] Intel(R) Trusted Execution Technology support: xen
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Thu, 30 Aug 2007 19:17:45 +0100
Cc: "Xu, James" <james.xu@xxxxxxxxx>, "Wang, Shane" <shane.wang@xxxxxxxxx>, "Wei, Gang" <gang.wei@xxxxxxxxx>, "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>
Delivery-date: Thu, 30 Aug 2007 11:18:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2FCC767.150ED%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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acfp01AFWEdUfIQmRfyDf3HETiYK8QBG4bGUAAwqiPAABACQxgAAfxviAAAkEHs=
Thread-topic: [Xen-devel] [RFC][PATCH][1/4] Intel(R) Trusted Execution Technology support: xen
User-agent: Microsoft-Entourage/
On 30/8/07 19:13, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> wrote:

>> That's all for now. The sboot module itself is scary big. :-/
> Actually, to that end, do you have any documentation to go with this
> patchset? It'd be kind of nice to know how to use sboot, what security
> guarantees it can provide, how to use the toolset, etc etc. Otherwise we're
> going to have 20kloc added to our tree that noone knows how to use! Which I
> think means some documentation has to be a pre-condition for acceptance.

The patch summary email is a nice start, by the way, but I think you need
something in our docs directory that goes into a bit more detail. Perhaps
some use cases for sboot? How to use the tools? A plain text file would be
fine -- it's just the content I care about.

 -- Keir

Xen-devel mailing list