All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Matthew.Fioravante@jhuapl.edu" <Matthew.Fioravante@jhuapl.edu>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"JBeulich@suse.com" <JBeulich@suse.com>,
	"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Subject: Re: [PATCH v5.1 01/12] mini-os/tpm{back, front}: Change shared page ABI
Date: Thu, 11 Apr 2013 10:11:31 -0400	[thread overview]
Message-ID: <5166C493.6040503@tycho.nsa.gov> (raw)
In-Reply-To: <1365688848.8126.0.camel@zakaz.uk.xensource.com>

On 04/11/2013 10:00 AM, Ian Campbell wrote:
> Is this in the wrong thread and should be in "[PATCH v5 00/12] vTPM
> updates for 4.3" as an update to
> <1363896689-11086-2-git-send-email-dgdegra@tycho.nsa.gov> ?
>

Yes, this is an update to that patch and should have also been sent in
reply to that thread.

> On Fri, 2013-03-22 at 22:30 +0000, Daniel De Graaf wrote:
>> This changes the vTPM shared page ABI from a copy of the Xen network
>> interface to a single-page interface that better reflects the expected
>> behavior of a TPM: only a single request packet can be sent at any given
>> time, and every packet sent generates a single response packet. This
>> protocol change should also increase efficiency as it avoids mapping and
>> unmapping grants when possible. The vtpm xenbus device now requires a
>> feature-protocol-v2 node in xenstore to avoid conflicts with existing
>> (xen-patched) kernels supporting the old interface.
>>
>> While the contents of the shared page have been defined to allow packets
>> larger than a single page (actually 4088 bytes) by allowing the client
>> to add extra grant references, the mapping of these extra references has
>> not been implemented; a feature node in xenstore may be used in the
>> future to indicate full support for the multi-page protocol. Most uses
>> of the TPM should not require this feature.
>>
>> Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
>> Cc: Jan Beulich <JBeulich@suse.com>
>>
>> ---
>>
>> Changes from v5: handle xenbus states properly, and keep the old header
>> contents intact.
>>
>> Changes from v4: use feature-protocol-v2 nodes instead of changing the
>> device name; add command cancellation support to the protocol.
>>

  reply	other threads:[~2013-04-11 14:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 22:28 [PATCH RFC] drivers/tpm: add xen tpmfront interface Daniel De Graaf
2013-03-22 22:30 ` [PATCH v5.1 01/12] mini-os/tpm{back, front}: Change shared page ABI Daniel De Graaf
2013-04-11 14:00   ` Ian Campbell
2013-04-11 14:11     ` Daniel De Graaf [this message]
2013-04-11 14:14   ` Ian Campbell
2013-04-11 14:38     ` Daniel De Graaf
2013-04-11 15:25       ` Ian Campbell
2013-04-11 15:46         ` Daniel De Graaf
2013-04-11 14:27   ` Ian Campbell
2013-04-11 15:10     ` Daniel De Graaf
2013-04-11 15:22       ` Ian Campbell
2013-04-11 16:18         ` Daniel De Graaf
2013-04-11 16:20           ` [PATCH v5.2] " Daniel De Graaf
2013-04-11 14:17 ` [PATCH RFC] drivers/tpm: add xen tpmfront interface Ian Campbell
2013-04-11 14:38   ` Daniel De Graaf

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=5166C493.6040503@tycho.nsa.gov \
    --to=dgdegra@tycho.nsa.gov \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Matthew.Fioravante@jhuapl.edu \
    --cc=konrad.wilk@oracle.com \
    --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 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.