From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Corey Bryant <coreyb@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] QMP: TPM QMP and man page documentation updates
Date: Mon, 18 Mar 2013 13:46:56 -0400 [thread overview]
Message-ID: <51475310.2060008@linux.vnet.ibm.com> (raw)
In-Reply-To: <878v5k65ur.fsf@blackfin.pond.sub.org>
On 03/18/2013 12:16 PM, Markus Armbruster wrote:
> Corey Bryant <coreyb@linux.vnet.ibm.com> writes:
>
>> Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
>> ---
>> qemu-options.hx | 3 ++-
>> qmp-commands.hx | 59 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 61 insertions(+), 1 deletion(-)
>>
>> diff --git a/qemu-options.hx b/qemu-options.hx
>> index 30fb85d..3b3cd0f 100644
>> --- a/qemu-options.hx
>> +++ b/qemu-options.hx
>> @@ -2237,7 +2237,8 @@ Backend type must be:
>> @option{passthrough}.
>>
>> The specific backend type will determine the applicable options.
>> -The @code{-tpmdev} option requires a @code{-device} option.
>> +The @code{-tpmdev} option creates the TPM backend and requires a
>> +@code{-device} option that specifies the TPM frontend interface model.
>>
>> Options to each backend are described below.
>>
>> diff --git a/qmp-commands.hx b/qmp-commands.hx
>> index b370060..4eda5ea 100644
>> --- a/qmp-commands.hx
>> +++ b/qmp-commands.hx
>> @@ -2721,18 +2721,77 @@ EQMP
>> .mhandler.cmd_new = qmp_marshal_input_query_tpm,
>> },
>>
>> +SQMP
>> +query-tpm
>> +---------
>> +
>> +Return information about the TPM device.
>> +
>> +Arguments: None
>> +
>> +Example:
>> +
>> +-> { "execute": "query-tpm" }
>> +<- { "return":
>> + [
>> + { "model": "tpm-tis",
>> + "tpm-options":
>> + { "type": "tpm-passthrough-options",
>> + "data":
>> + { "cancel-path": "/sys/class/misc/tpm0/device/cancel",
>> + "path": "/dev/tpm0"
>> + }
>> + },
>> + "type": "passthrough",
>> + "id": "tpm0"
>> + }
>> + ]
>> + }
>> +
>> +EQMP
>> +
> "tpm-options" is a discriminated union. How is its discriminator "type"
> (here: "tpm-passthrough-options") related to the outer "type" (here:
> "passthrough")?
It gives you similar information twice. So there is a direct
relationship between the two types.
next prev parent reply other threads:[~2013-03-18 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 17:17 [Qemu-devel] [PATCH] QMP: TPM QMP and man page documentation updates Corey Bryant
2013-03-15 17:54 ` Eric Blake
2013-03-18 16:16 ` Markus Armbruster
2013-03-18 17:46 ` Stefan Berger [this message]
2013-03-18 18:35 ` Corey Bryant
2013-03-19 7:26 ` Markus Armbruster
2013-03-19 14:59 ` Corey Bryant
2013-03-20 12:32 ` Markus Armbruster
2013-03-20 13:26 ` Corey Bryant
2013-03-20 16:36 ` Corey Bryant
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=51475310.2060008@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=lcapitulino@redhat.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).