From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Matthew Fioravante <matthew.fioravante@jhuapl.edu>
Cc: "samuel.thibault@ens-lyon.org" <samuel.thibault@ens-lyon.org>,
"Ian.Jackson@eu.citrix.com" <Ian.Jackson@eu.citrix.com>,
"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2 0/9] vTPM new ABI, extensions
Date: Tue, 04 Dec 2012 14:00:29 -0500 [thread overview]
Message-ID: <50BE484D.2060208@tycho.nsa.gov> (raw)
In-Reply-To: <50BE4734.7070108@jhuapl.edu>
On 12/04/2012 01:55 PM, Matthew Fioravante wrote:
> Have you given any thought to the vtpm auto-shutdown semantics? I'd like to preserve that if at all possible. Is the only conflicting patch there patch 8?
>
#8 should be the only patch that conflicts, although I have not tested
that the shutdown works as expected after #5. I think the shutdown key
in Xenstore is the best solution for this issue (and don't really have
a strong preference for weak function vs a waitqueue).
> On 11/30/2012 09:49 AM, Daniel De Graaf wrote:
>> This patch queue goes on top of Matthew Fioravante's [VTPM v5 0/7]
>> series. While some of the patches have been posted before, all have
>> been cleaned up a bit.
>>
>> [PATCH 1/9] stubdom: Change vTPM shared page ABI
>> * Removed unneeded reconfiguration pieces
>> * Removed feature-protocol-v2 xenstore key references
>>
>> [PATCH 2/9] stubdom/vtpm: Support locality field
>> * Add distinct patch file instead of patching a patch
>> * Comment on future use of the locality field
>>
>> [PATCH 3/9] stubdom/vtpm: correct the buffer size returned by
>> * New patch
>>
>> [PATCH 4/9] stubdom/vtpm: Add locality-5 PCRs
>> * New patch
>>
>> [PATCH 5/9] stubdom/vtpm: Allow repoen of closed devices
>> * This used to use Reconfigure, but has been changed to use
>> the Closed states similar to blkback
>>
>> [PATCH 6/9] stubdom/vtpm: make state save operation atomic
>> * Avoid hardcoded maximum saved state size
>> * Better debug/error messages
>>
>> [PATCH 7/9] stubdom/grub: send kernel measurements to vTPM
>> * Use PolarSSL SHA1 function
>> * Use byteswap.h functions
>>
>> [PATCH 8/9] stubdom/vtpm: support multiple backends
>> * Split into its own patch so it can be excluded if
>> automatic vTPM shutdown is required
>>
>> [PATCH 9/9] stubdom/vtpm: Add PCR pass-through to hardware TPM
>> * New patch, RFC; an alternative to hwinitpcrs
>
>
--
Daniel De Graaf
National Security Agency
prev parent reply other threads:[~2012-12-04 19:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 14:49 [PATCH v2 0/9] vTPM new ABI, extensions Daniel De Graaf
2012-11-30 14:49 ` [PATCH 1/9] stubdom: Change vTPM shared page ABI Daniel De Graaf
2012-11-30 14:49 ` [PATCH 2/9] stubdom/vtpm: Support locality field Daniel De Graaf
2012-12-04 17:43 ` Matthew Fioravante
2012-11-30 14:49 ` [PATCH 3/9] stubdom/vtpm: correct the buffer size returned by TPM_CAP_PROP_INPUT_BUFFER Daniel De Graaf
2012-11-30 14:49 ` [PATCH 4/9] stubdom/vtpm: Add locality-5 PCRs Daniel De Graaf
2012-11-30 14:49 ` [PATCH 5/9] stubdom/vtpm: Allow repoen of closed devices Daniel De Graaf
2012-11-30 14:49 ` [PATCH 6/9] stubdom/vtpm: make state save operation atomic Daniel De Graaf
2012-11-30 14:49 ` [PATCH 7/9] stubdom/grub: send kernel measurements to vTPM Daniel De Graaf
2012-12-04 0:17 ` Samuel Thibault
2012-12-04 17:44 ` Matthew Fioravante
2012-11-30 14:49 ` [PATCH 8/9] stubdom/vtpm: support multiple backends Daniel De Graaf
2012-11-30 14:49 ` [PATCH 9/9] stubdom/vtpm: Add PCR pass-through to hardware TPM Daniel De Graaf
2012-12-04 17:47 ` Matthew Fioravante
2012-12-04 18:43 ` Daniel De Graaf
2012-12-04 18:53 ` Matthew Fioravante
2012-12-04 0:18 ` [PATCH v2 0/9] vTPM new ABI, extensions Samuel Thibault
2012-12-04 18:55 ` Matthew Fioravante
2012-12-04 19:00 ` Daniel De Graaf [this message]
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=50BE484D.2060208@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=matthew.fioravante@jhuapl.edu \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).