From: James Bottomley <jejb@linux.ibm.com>
To: "Stefan Berger" <stefanb@linux.ibm.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v6 2/2] tpm: add backend for mssim
Date: Mon, 25 Sep 2023 08:12:16 -0400 [thread overview]
Message-ID: <db47b1e842d94994d0844021a4ab5423c9525a83.camel@linux.ibm.com> (raw)
In-Reply-To: <b2d53350-ce67-4c29-5d3d-6dee6484c8ed@linux.ibm.com>
On Fri, 2023-09-22 at 09:27 -0400, Stefan Berger wrote:
>
> On 9/22/23 09:02, Daniel P. Berrangé wrote:
> > On Fri, Sep 22, 2023 at 08:41:19AM -0400, Stefan Berger wrote:
> > > On 9/22/23 02:00, Markus Armbruster wrote:
> > > > Found this cleaning out old mail, sorry for missing it until
> > > > now!
> > > >
> > > > I think we owe James a quick decision wether we're willing to
> > > > take the feature. Stefan, thoughts?
> > > I thought we discusses it back then. Does it handle snapshotting
> > > and migration correctly?
> > To quote the patch itself:
> >
> > +The mssim backend supports snapshotting and migration, but the
> > state
> > +of the Microsoft Simulator server must be preserved (or the
> > server
> > +kept running) outside of QEMU for restore to be successful.
>
> How does 'it' support snapshotting where the state of the TPM can be
> completely different depending on the snapshot?
In the same way we support things like external disk devices across
snapshot and migration: it's up to the owner of the device to preserve
the state for the next resume. If you muck with the state (or connect
the wrong device) all bets are off.
> I know what it took to support this feature with swtpm/libtpms but
> I don't see the equivalent here in this backend driver nor in the TCG
> reference code that the underlying TPM 2 simulator is based upon.
>
> I do not want to stand in the way of it being merged but please
> understand that I will also neither maintain nor fix bugs related to
> it nor its related underlying simulator -- with James being the
> maintainer of it, this should be clear. I have reason why I am saying
> this and they come from dealing with the upstream TPM 2 reference
> code.
I already said I'll support this, and added a Maintainers entry and a
specific exclusion from your TPM maintainer entry. I'm not sure what
additional assurances I can give?
James
next prev parent reply other threads:[~2023-09-25 12:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 16:15 [PATCH v6 0/2] tpm: add mssim backend James Bottomley
2023-01-09 16:15 ` [PATCH v6 1/2] tpm: convert tpmdev options processing to new visitor format James Bottomley
2023-09-26 15:20 ` Stefan Berger
2023-09-26 17:43 ` Stefan Berger
2023-01-09 16:15 ` [PATCH v6 2/2] tpm: add backend for mssim James Bottomley
2023-09-22 6:00 ` Markus Armbruster
2023-09-22 12:41 ` Stefan Berger
2023-09-22 13:02 ` Daniel P. Berrangé
2023-09-22 13:27 ` Stefan Berger
2023-09-25 12:12 ` James Bottomley [this message]
2023-09-25 12:15 ` James Bottomley
2023-09-25 12:25 ` 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=db47b1e842d94994d0844021a4ab5423c9525a83.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).