qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <jejb@linux.ibm.com>
To: "Stefan Berger" <stefanb@linux.ibm.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH] tpm: add backend for mssim
Date: Mon, 12 Dec 2022 17:27:02 -0500	[thread overview]
Message-ID: <289ef2dceb2d94312019d288a3b49c4e786df934.camel@linux.ibm.com> (raw)
In-Reply-To: <f7119c81-e571-382b-84c6-628747cd9e0b@linux.ibm.com>

On Mon, 2022-12-12 at 17:02 -0500, Stefan Berger wrote:
> 
> 
> On 12/12/22 16:36, James Bottomley wrote:
> > On Mon, 2022-12-12 at 14:32 -0500, Stefan Berger wrote:
[...]
> > >   Either way, what is the latency that this introduces because I
> > > would expect that this slows down IMA since the PCR extensions &
> > > TPM 2 response now go back and forth across the network?
> > 
> > Most data centre protocols are now encrypted and networked (NVMeoF
> > would probably be the poster child) with no real ill effects.  In
> > terms of a TPM, the competition is an underpowered discrete chip
> > over a slow serial bus, so I think we'll actually improve the
> > latency not diminish it.
> 
> Compared to QEMU and swtpm talking over a local socket you probably
> have a decent amount of slow-down if this is over the network.

I can only repeat that doesn't happen with other much more volume and
latency bound networked protocols.

> I still fail to see the advantage over what we have at the moment.
> Also I don't see what advantage the mssim protocol brings over what
> swtpm provides.

I think I've said a couple of times now: The primary advantage is that
it talks to the reference implementation over its native protocol.

>  If you are willing to do a 'dnf -y install swtpm_setup' and start
> the VM via libvirt it really doesn't matter what protocol the TPM is
> running underneath since it's all transparent.

Swtpm currently isn't building for Leap:

https://build.opensuse.org/package/show/security/swtpm

And, as I said, this is primarily for testing, so I need the reference
implementation ... swtpm has started deviating from it.

James





  reply	other threads:[~2022-12-12 22:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10 17:10 [PATCH] tpm: add backend for mssim James Bottomley
2022-12-12 13:43 ` Stefan Berger
2022-12-12 13:59   ` James Bottomley
2022-12-12 14:27     ` Stefan Berger
2022-12-12 14:32       ` James Bottomley
2022-12-12 14:44         ` Stefan Berger
2022-12-12 14:47           ` James Bottomley
2022-12-12 15:20             ` Stefan Berger
2022-12-12 15:28               ` James Bottomley
2022-12-12 15:46                 ` Stefan Berger
2022-12-12 15:47 ` Daniel P. Berrangé
2022-12-12 16:38   ` James Bottomley
2022-12-12 16:59     ` Stefan Berger
2022-12-12 18:48       ` James Bottomley
2022-12-12 18:58         ` Stefan Berger
2022-12-12 19:12           ` James Bottomley
2022-12-12 19:32             ` Stefan Berger
2022-12-12 20:24               ` Stefan Berger
2022-12-12 21:36               ` James Bottomley
2022-12-12 22:02                 ` Stefan Berger
2022-12-12 22:27                   ` James Bottomley [this message]
2022-12-12 22:43                     ` Stefan Berger
2022-12-14 11:52                   ` Daniel P. Berrangé
2022-12-14 12:43                     ` James Bottomley
2022-12-15  2:42                       ` Stefan Berger
2022-12-14 11:55           ` Daniel P. Berrangé
2022-12-12 22:06   ` James Bottomley
2022-12-14 11:31     ` Daniel P. Berrangé
2022-12-14 12:47       ` James Bottomley
2022-12-14 14:17         ` Markus Armbruster

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=289ef2dceb2d94312019d288a3b49c4e786df934.camel@linux.ibm.com \
    --to=jejb@linux.ibm.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanb@linux.ibm.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).