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
