From: Keir Fraser <keir@xensource.com>
To: "Cihula, Joseph" <joseph.cihula@intel.com>,
xen-devel@lists.xensource.com, xense-devel@lists.xensource.com
Cc: "Xu, James" <james.xu@intel.com>,
"Wang, Shane" <shane.wang@intel.com>,
"Wei, Gang" <gang.wei@intel.com>,
"Zhai, Edwin" <edwin.zhai@intel.com>
Subject: Re: [RFC][PATCH][1/4] Intel(R) Trusted Execution Technology support: xen
Date: Thu, 30 Aug 2007 19:17:45 +0100 [thread overview]
Message-ID: <C2FCC859.150EF%keir@xensource.com> (raw)
In-Reply-To: <C2FCC767.150ED%Keir.Fraser@cl.cam.ac.uk>
On 30/8/07 19:13, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> 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
next prev parent reply other threads:[~2007-08-30 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D936D925018D154694D8A362EEB0892002463CFC@orsmsx416.amr.corp.intel.com>
2007-08-30 10:16 ` [RFC][PATCH][1/4] Intel(R) Trusted Execution Technology support: xen Keir Fraser
2007-08-30 16:17 ` Cihula, Joseph
2007-08-30 17:59 ` Keir Fraser
2007-08-30 18:13 ` Keir Fraser
2007-08-30 18:17 ` Keir Fraser [this message]
2007-08-31 11:19 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C2FCC859.150EF%keir@xensource.com \
--to=keir@xensource.com \
--cc=edwin.zhai@intel.com \
--cc=gang.wei@intel.com \
--cc=james.xu@intel.com \
--cc=joseph.cihula@intel.com \
--cc=shane.wang@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xense-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.