From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>
Cc: andreas.niederl@iaik.tugraz.at, qemu-devel@nongnu.org,
anthony@codemonkey.ws, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V19 1/7] Support for TPM command line options
Date: Mon, 12 Nov 2012 08:04:10 -0500 [thread overview]
Message-ID: <50A0F3CA.5090009@linux.vnet.ibm.com> (raw)
In-Reply-To: <509BD554.1080708@linux.vnet.ibm.com>
On 11/08/2012 10:52 AM, Corey Bryant wrote:
>
>
> On 10/24/2012 03:06 PM, Stefan Berger wrote:
>> On 09/27/2012 10:12 AM, Corey Bryant wrote:
>>>
>>>
>>> On 06/04/2012 03:37 PM, Stefan Berger wrote:
>>
>>>> + if (!QLIST_EMPTY(&tpm_backends)) {
>>>> + error_report("Only one TPM is allowed.\n");
>>>> + return 1;
>>>> + }
>>>
>>> A list of tpm_backends is maintained and walked in a few places, but
>>> only one is allowed to be added to the list. Will it ever make sense
>>> to enable multiple backends at one time?
>>>
>>
>> A list is also returned through the monitor. This list can at the moment
>> only have maximum of one entry. I would keep that list there unless
>> someone else opposes. It may be possible to create different types of
>> hardware emulation interfaces or simply replicate the TPM TIS at
>> different addresses. So I cannot say whether it will 'ever make sense'
>> to do that but I'd rather keep the opportunity there than close it and
>> with that also let the monitor return a list of items rather than a
>> single item.
>>
>> I removed the processing of the lists in this part of the code at least.
>>
>
> Ok and it doesn't hurt to keep the list processing. In that case you
> might as well keep the list processing code everywhere that you
> already have it.
>
I was only going to keep it in the monitor part now...
+ */
>>>> +int tpm_config_parse(QemuOptsList *opts_list, const char *optarg)
>>>> +{
>>>> + QemuOpts *opts;
>>>> +
>>>> + if (strcmp("none", optarg) != 0) {
>>>
>>> What's the point of supporting "-tpmdev none"?
>>>
>>
>> Removed.
>>
>
> There must have been a reason you added it in the first place that I'm
> just not aware of. Did someone else suggest adding it?
Not that I can remember.The option would have been useful if every VM by
default had a TPM, similar to the physical world today, but it's
unlikely that this will happen.
Regards,
Stefan
next prev parent reply other threads:[~2012-11-12 13:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 19:37 [Qemu-devel] [PATCH V19 0/7] Qemu Trusted Platform Module (TPM) integration Stefan Berger
2012-06-04 19:37 ` [Qemu-devel] [PATCH V19 1/7] Support for TPM command line options Stefan Berger
2012-09-27 14:12 ` Corey Bryant
2012-10-24 19:06 ` Stefan Berger
2012-11-08 15:52 ` Corey Bryant
2012-11-12 13:04 ` Stefan Berger [this message]
2012-06-04 19:37 ` [Qemu-devel] [PATCH V19 2/7] Add TPM (frontend) hardware interface (TPM TIS) to Qemu Stefan Berger
2012-09-27 14:22 ` Corey Bryant
2012-10-24 18:46 ` Stefan Berger
2012-11-08 15:39 ` Corey Bryant
2012-11-12 13:16 ` Stefan Berger
2012-11-12 18:48 ` Corey Bryant
2012-10-03 18:35 ` Corey Bryant
2012-06-04 19:37 ` [Qemu-devel] [PATCH V19 3/7] Add a debug register Stefan Berger
2012-09-27 14:23 ` Corey Bryant
2012-06-04 19:37 ` [Qemu-devel] [PATCH V19 4/7] Build the TPM frontend code Stefan Berger
2012-09-27 14:24 ` Corey Bryant
2012-06-04 19:37 ` [Qemu-devel] [PATCH V19 5/7] Add a TPM Passthrough backend driver implementation Stefan Berger
2012-09-27 14:28 ` Corey Bryant
2012-10-24 19:07 ` Stefan Berger
2012-06-04 19:37 ` [Qemu-devel] [PATCH V19 6/7] Introduce --enable-tpm-passthrough configure option Stefan Berger
2012-09-27 14:29 ` Corey Bryant
2012-06-04 19:37 ` [Qemu-devel] [PATCH V19 7/7] Add fd parameter for TPM passthrough driver Stefan Berger
2012-09-27 14:35 ` Corey Bryant
2012-10-03 18:46 ` Corey Bryant
2012-10-24 19:06 ` Stefan Berger
2012-06-04 19:56 ` [Qemu-devel] [PATCH V19 0/7] Qemu Trusted Platform Module (TPM) integration Stefan Weil
2012-06-04 23:08 ` Anthony Liguori
2012-09-27 14:59 ` Corey Bryant
2012-09-28 22:43 ` Stefan Berger
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=50A0F3CA.5090009@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=andreas.niederl@iaik.tugraz.at \
--cc=anthony@codemonkey.ws \
--cc=coreyb@linux.vnet.ibm.com \
--cc=mst@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).