From: "Michael S. Tsirkin" <mst@redhat.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: dgreid@chromium.org,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
virtualization@lists.linux-foundation.org,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-integrity@vger.kernel.org, Peter Huewe <peterhuewe@gmx.de>,
apronin@chromium.org, David Tolnay <dtolnay@gmail.com>
Subject: Re: [PATCH] tpm: Add driver for TPM over virtio
Date: Fri, 22 Feb 2019 16:16:01 -0500 [thread overview]
Message-ID: <20190222160220-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1550849416.2787.5.camel@HansenPartnership.com>
On Fri, Feb 22, 2019 at 07:30:16AM -0800, James Bottomley wrote:
> On Thu, 2019-02-21 at 18:14 -0800, David Tolnay wrote:
> > Add a config TCG_VIRTIO_VTPM which enables a driver providing the
> > guest kernel side of TPM over virtio.
>
> What's the use case for using this over the current non-virtio vTPM?.
> I always thought virtio was about guest to host transport efficiency,
> but the phsical TPM, being connected over a very slow bus, is about as
> inefficient as you can get in that regard, so why do we need to use
> virtio to drive the virtual one?
I can't say for sure about TPM.
But generally there are many reasons to do virtio rather than emulating
a hardware device.
Ease of extending the device could be one. E.g. what if you want to make
an extension that hardware does not support? You are at cross-purposes
with a hardware vendor who can happen to be the driver maintainer as
well.
A decent specification and readiness to fix bugs in the right place
(e.g. driver violates spec? we'll fix driver not as you to work around
it in the device) is another.
You can also download the spec without clicking I agree once - and it
follows the Non-Assertion IPR Mode to help people not get sued.
Stuff like that is conductive to getting things done.
--
MST
next prev parent reply other threads:[~2019-02-22 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <388c5b80-21a7-1e91-a11f-3a1c1432368b@gmail.com>
2019-02-22 5:51 ` [PATCH] tpm: Add driver for TPM over virtio Michael S. Tsirkin
[not found] ` <461bd10a-0a30-81e3-63b4-0798eb75b9e7@gmail.com>
2019-02-22 22:24 ` Michael S. Tsirkin
[not found] ` <20190222102610.GB5613@linux.intel.com>
2019-02-22 15:23 ` Michael S. Tsirkin
[not found] ` <20190222193156.GA6475@linux.intel.com>
2019-02-22 20:55 ` Michael S. Tsirkin
[not found] ` <20190222193305.GB6475@linux.intel.com>
2019-02-22 21:25 ` Michael S. Tsirkin
[not found] ` <20190222215001.GA21427@linux.intel.com>
[not found] ` <f16bd565-0a7e-d7bb-a5e8-eda48ac8de80@gmail.com>
[not found] ` <20190222223634.GA27601@linux.intel.com>
2019-02-22 23:05 ` Michael S. Tsirkin
[not found] ` <1550849416.2787.5.camel@HansenPartnership.com>
2019-02-22 21:16 ` Michael S. Tsirkin [this message]
[not found] ` <20190222213137.GZ17500@ziepe.ca>
[not found] ` <20190222215923.GB21427@linux.intel.com>
2019-02-22 22:07 ` 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=20190222160220-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=apronin@chromium.org \
--cc=dgreid@chromium.org \
--cc=dtolnay@gmail.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=virtualization@lists.linux-foundation.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).