qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: "Patrick Ohly" <patrick.ohly@intel.com>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Amarnath Valluri <amarnath.valluri@intel.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 9/9] tpm: Added support for TPM emulator
Date: Mon, 10 Apr 2017 12:14:10 -0400	[thread overview]
Message-ID: <df1081c7-7f3b-20df-0ff0-a2c2e6de9e43@linux.vnet.ibm.com> (raw)
In-Reply-To: <1491818850.10884.99.camel@intel.com>

On 04/10/2017 06:07 AM, Patrick Ohly wrote:
> On Mon, 2017-04-10 at 09:54 +0000, Marc-André Lureau wrote:
>
>> By "public protocol", I mean qemu communication with a foreign
>> project, swtpm or other.
>>
>> If qemu grows new needs, or if the protocol is found limited or buggy,
>> it may change. Subtle interactions may break between various
>> implementations.  The minimum would be some versioning or
>> capabilities. A document describing the states and messages
>> allowed/denied & effects would be quite necessary.
> Stefan, is there any documentation besides the source?

No.

>
> Just asking, I don't think it is needed because...
>
>> Otoh, there doesn't seem to be other users of this protocol, or other
>> implementations. So it may make sense to make it qemu-specific, and
>> thus "private": the protocol and implementation can evolve without
>> risk to break other users. This gives us a lot more flexibility and
>> control, and doesn't have to be very strictly documented (although it
>> is still better to be strict, but requires more effort).
> ... I suspect it falls into this camp. I can't think of any users of the
> protocol besides swtpm itself and now qemu. Stefan, is that correct?
>

Correct. Only swtpm client tools (swtpm_ioctl) and now your QEMU patches 
are using the protocol.

  reply	other threads:[~2017-04-10 16:14 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 14:30 [Qemu-devel] [PATCH v2 0/9] Provide support for the software TPM Amarnath Valluri
2017-04-07 14:30 ` [Qemu-devel] [PATCH v2 1/9] tpm-backend: Remove unneeded member variable from backend class Amarnath Valluri
2017-04-25 18:19   ` Stefan Berger
2017-04-07 14:30 ` [Qemu-devel] [PATCH v2 2/9] tpm-backend: Move thread handling inside TPMBackend Amarnath Valluri
2017-04-25 18:21   ` Stefan Berger
2017-04-07 14:30 ` [Qemu-devel] [PATCH v2 3/9] tpm-backend: Initialize and free data members in it's own methods Amarnath Valluri
2017-04-25 18:27   ` Stefan Berger
2017-05-02  7:09     ` Amarnath Valluri
2017-04-07 14:30 ` [Qemu-devel] [PATCH v2 4/9] tpm-backend: Made few interface methods optional Amarnath Valluri
2017-04-25 18:29   ` Stefan Berger
2017-04-07 14:30 ` [Qemu-devel] [PATCH v2 5/9] tmp backend: Add new api to read backend TpmInfo Amarnath Valluri
2017-04-25 18:51   ` Stefan Berger
2017-04-25 18:59     ` Eric Blake
2017-05-02  7:17       ` Amarnath Valluri
2017-04-07 14:30 ` [Qemu-devel] [PATCH v2 6/9] tpm-backend: Remove unneeded destroy() method from TpmDriverOps interface Amarnath Valluri
2017-04-25 18:59   ` Stefan Berger
2017-05-02  7:42     ` Amarnath Valluri
2017-04-07 14:30 ` [Qemu-devel] [PATCH v2 7/9] tpm-backend: Move realloc_buffer() implementation to base class Amarnath Valluri
2017-04-25 19:01   ` Stefan Berger
2017-04-07 14:30 ` [Qemu-devel] [PATCH v2 8/9] tpm-passthrough: move reusable code to utils Amarnath Valluri
2017-04-25 19:09   ` Stefan Berger
2017-04-07 14:30 ` [Qemu-devel] [PATCH v2 9/9] tpm: Added support for TPM emulator Amarnath Valluri
2017-04-07 14:41   ` Daniel P. Berrange
2017-04-07 15:11     ` Marc-André Lureau
2017-04-10  7:34       ` Amarnath Valluri
2017-04-10  9:54         ` Marc-André Lureau
2017-04-10 10:07           ` Patrick Ohly
2017-04-10 16:14             ` Stefan Berger [this message]
2017-04-10 21:11               ` Stefan Berger
2017-04-10  7:08     ` Amarnath Valluri
2017-04-10  8:31       ` Daniel P. Berrange
2017-04-10 16:15       ` Stefan Berger
2017-04-25 19:35   ` Stefan Berger
2017-04-12 23:52 ` [Qemu-devel] [PATCH v2 0/9] Provide support for the software TPM no-reply

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=df1081c7-7f3b-20df-0ff0-a2c2e6de9e43@linux.vnet.ibm.com \
    --to=stefanb@linux.vnet.ibm.com \
    --cc=amarnath.valluri@intel.com \
    --cc=berrange@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=patrick.ohly@intel.com \
    --cc=qemu-devel@nongnu.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).