From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: anbang.ruan@cs.ox.ac.uk, andreas.niederl@iaik.tugraz.at,
qemu-devel@nongnu.org, serge@hallyn.com
Subject: Re: [Qemu-devel] [PATCH V11 0/5] Qemu Trusted Platform Module (TPM) integration
Date: Sun, 02 Oct 2011 16:12:14 -0400 [thread overview]
Message-ID: <4E88C59E.2020209@linux.vnet.ibm.com> (raw)
In-Reply-To: <20111002113835.GH30747@redhat.com>
On 10/02/2011 07:38 AM, Michael S. Tsirkin wrote:
> On Wed, Sep 28, 2011 at 09:22:55AM -0400, Stefan Berger wrote:
>> The following series of patches adds TPM (Trusted Platform Module) support
>> to Qemu. An emulator for the TIS (TPM Interface Spec) interface is
>> added that provides the basis for accessing a 'backend' implementing the actual
>> TPM functionality. The TIS emulator serves as a 'frontend' enabling for
>> example Linux's TPM TIS (tpm_tis) driver.
>>
>> In this series I am posting a backend implementation that makes use of the
>> host's TPM through a passthrough driver, which on Linux is accessed
>> using /dev/tpm0.
> Looks pretty clean, ACK to patches 1-4.
Thanks.
> The passthrough mode is quite easy to misuse, though most
> of the problem is in the hardware, not on our side.
>
> I'm still trying to think of a good way to warn users
> about the pitfalls with that. Disabling by default in configure, unless
The documentation isn't enough? If it's really needed could I add
another patch on top of the existing V11?
> explictly required, is certainly one way.
> And/or, let's rename it 'assigned' mode to resemble the name of
> another fragile qemu feature :) Only half joking ...
>
Well, not sure what exactly you mean, but some things seem late versus
closing time...
Stefan
next prev parent reply other threads:[~2011-10-02 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 13:22 [Qemu-devel] [PATCH V11 0/5] Qemu Trusted Platform Module (TPM) integration Stefan Berger
2011-09-28 13:22 ` [Qemu-devel] [PATCH V11 1/5] Support for TPM command line options Stefan Berger
2011-09-28 13:22 ` [Qemu-devel] [PATCH V11 2/5] Add TPM (frontend) hardware interface (TPM TIS) to Qemu Stefan Berger
2011-09-28 13:22 ` [Qemu-devel] [PATCH V11 3/5] Add a debug register Stefan Berger
2011-09-28 13:22 ` [Qemu-devel] [PATCH V11 4/5] Build the TPM frontend code Stefan Berger
2011-09-28 13:23 ` [Qemu-devel] [PATCH V11 5/5] Add a TPM Passthrough backend driver implementation Stefan Berger
2011-10-02 11:30 ` Michael S. Tsirkin
2011-10-02 11:38 ` [Qemu-devel] [PATCH V11 0/5] Qemu Trusted Platform Module (TPM) integration Michael S. Tsirkin
2011-10-02 20:12 ` Stefan Berger [this message]
2011-10-02 21:05 ` Michael S. Tsirkin
2011-10-04 18:44 ` [Qemu-devel] [PATCH 6/5] Introduce --enable-tpm-passthrough configure option Stefan Berger
2011-10-04 18:44 ` [Qemu-devel] [PATCH 7/5] Move parsing of filedescriptor into common function Stefan Berger
2011-10-04 18:45 ` [Qemu-devel] [PATCH 8/5] Add fd parameter for TPM passthrough driver 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=4E88C59E.2020209@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).