From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: serge@hallyn.com, qemu-devel@nongnu.org, anbang.ruan@cs.ox.ac.uk,
andreas.niederl@iaik.tugraz.at
Subject: Re: [Qemu-devel] [PATCH V9 5/5] Add a TPM Passthrough backend driver implementation
Date: Mon, 26 Sep 2011 22:20:13 -0400 [thread overview]
Message-ID: <4E8132DD.6030601@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110926202430.GA23402@redhat.com>
On 09/26/2011 04:24 PM, Michael S. Tsirkin wrote:
> On Mon, Sep 26, 2011 at 04:12:19PM -0400, Stefan Berger wrote:
>
>>>> + if (tpm_passthrough_test_tpmdev(tb->s.tpm_pt->tpm_fd)) {
>>>> + fprintf(stderr,
>>>> + "'%s' is not a TPM device.\n",
>>>> + tb->s.tpm_pt->tpm_dev);
>>>> + goto err_close_tpmdev;
>>> Is this a must? Is it common to have more than one
>>> tpm device available on a computer? Maybe there's
>>> a good default in case only one tpm exists there ...
>>>
>> Well, passing /dev/tty48 in the place of /dev/tpm0 ends up in a
>> disappointment. So I'd rather check what that device is and refuse
>> to start if it is found not to be a TPM.
> Sorry, I mean can path= be made optional in case there's a single
> /dev/tmpXXX? Is it even common to have any tpms except
> /dev/tpm0?
No, typically there is only one TPM in the machine and it's accessible
using /dev/tpm0. SR-IOV TPMs afaik don't exist. So, yes, I am adding
'/dev/tpm0' as the default now.
>
> All good answers shall likely go into the documentation :)
I'll write about it... Will likely post v10 tomorrow.
Stefan
next prev parent reply other threads:[~2011-09-27 2:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 16:35 [Qemu-devel] [PATCH V9 0/5] Qemu Trusted Platform Module (TPM) integration Stefan Berger
2011-09-26 16:35 ` [Qemu-devel] [PATCH V9 1/5] Support for TPM command line options Stefan Berger
2011-09-26 19:03 ` Michael S. Tsirkin
2011-09-26 23:33 ` Stefan Berger
2011-09-26 16:35 ` [Qemu-devel] [PATCH V9 2/5] Add TPM (frontend) hardware interface (TPM TIS) to Qemu Stefan Berger
2011-09-26 19:09 ` Michael S. Tsirkin
2011-09-26 19:09 ` Avi Kivity
2011-09-27 1:48 ` Stefan Berger
2011-09-27 5:28 ` Michael S. Tsirkin
2011-09-26 16:35 ` [Qemu-devel] [PATCH V9 3/5] Add a debug register Stefan Berger
2011-09-26 16:35 ` [Qemu-devel] [PATCH V9 4/5] Build the TPM frontend code Stefan Berger
2011-09-26 16:35 ` [Qemu-devel] [PATCH V9 5/5] Add a TPM Passthrough backend driver implementation Stefan Berger
2011-09-26 19:20 ` Michael S. Tsirkin
2011-09-26 20:12 ` Stefan Berger
2011-09-26 20:24 ` Michael S. Tsirkin
2011-09-27 2:20 ` Stefan Berger [this message]
2011-09-26 19:22 ` [Qemu-devel] [PATCH V9 0/5] Qemu Trusted Platform Module (TPM) integration Michael S. Tsirkin
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=4E8132DD.6030601@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=anbang.ruan@cs.ox.ac.uk \
--cc=andreas.niederl@iaik.tugraz.at \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=serge@hallyn.com \
/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).