From: Stefan Berger <stefanb@linux.ibm.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: jejb@linux.ibm.com, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH 2/2] tpm: add backend for mssim
Date: Fri, 16 Dec 2022 09:55:26 -0500 [thread overview]
Message-ID: <1ee8a9cb-ba2c-60d0-a150-9710270020b7@linux.ibm.com> (raw)
In-Reply-To: <Y5yAz0qzaIW4HwFi@redhat.com>
On 12/16/22 09:29, Daniel P. Berrangé wrote:
>
> All the objections you're raising are related to the current
> specifics of the implementation of the mssim remote server.
> While valid, this is of no concern to QEMU when deciding whether
> to require a migration blocker on the client side. This is 3rd
> party remote service that should be considered a black box from
> QEMU's POV. It is possible to write a remote server that supports
> the mssim network protocol, and has the ability to serialize
> its state. Whether such an impl exists today or not is separate.
Then let's document the scenarios so someone can repeat them, I think this is just fair. James said he tested state migration scenarios and it works, so let's enable others to do it as well. I am open to someone maintaining just this driver and the dynamics that may develop around it.
Regards,
Stefan
> With regards,
> Daniel
next prev parent reply other threads:[~2022-12-16 14:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 18:01 [PATCH 0/2] tpm: add mssim backend James Bottomley
2022-12-15 18:01 ` [PATCH 1/2] tpm: convert tpmdev options processing to new visitor format James Bottomley
2022-12-15 18:01 ` [PATCH 2/2] tpm: add backend for mssim James Bottomley
2022-12-15 18:46 ` Stefan Berger
2022-12-15 19:22 ` James Bottomley
2022-12-15 19:35 ` Stefan Berger
2022-12-15 19:40 ` James Bottomley
2022-12-15 19:57 ` Stefan Berger
2022-12-15 20:07 ` James Bottomley
2022-12-15 20:22 ` Stefan Berger
2022-12-15 20:30 ` James Bottomley
2022-12-15 20:53 ` Stefan Berger
2022-12-16 10:27 ` Daniel P. Berrangé
2022-12-16 12:28 ` Stefan Berger
2022-12-16 12:54 ` Daniel P. Berrangé
2022-12-16 13:32 ` Stefan Berger
2022-12-16 13:53 ` James Bottomley
2022-12-16 14:01 ` Stefan Berger
2022-12-19 11:49 ` Stefan Berger
2022-12-19 13:02 ` James Bottomley
2022-12-19 14:01 ` Stefan Berger
2022-12-16 14:29 ` Daniel P. Berrangé
2022-12-16 14:55 ` Stefan Berger [this message]
2022-12-16 15:48 ` James Bottomley
2022-12-16 16:08 ` Stefan Berger
2022-12-16 16:13 ` James Bottomley
2022-12-16 16:21 ` Stefan Berger
2023-01-09 16:59 ` Dr. David Alan Gilbert
2023-01-09 17:43 ` James Bottomley
2023-01-09 17:52 ` Dr. David Alan Gilbert
2023-01-09 17:55 ` James Bottomley
2023-01-09 18:34 ` Stefan Berger
2023-01-09 18:51 ` James Bottomley
2023-01-09 18:54 ` Dr. David Alan Gilbert
2023-01-09 18:59 ` James Bottomley
2023-01-09 19:01 ` Stefan Berger
2023-01-09 21:06 ` Stefan Berger
2023-01-10 14:14 ` James Bottomley
2023-01-10 14:47 ` Stefan Berger
2023-01-10 14:55 ` James Bottomley
2023-01-10 15:00 ` 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=1ee8a9cb-ba2c-60d0-a150-9710270020b7@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jejb@linux.ibm.com \
--cc=qemu-devel@nongnu.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).