From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "John G Johnson" <john.g.johnson@oracle.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
quintela@redhat.com, "Jason Wang" <jasowang@redhat.com>,
"Felipe Franciosi" <felipe@nutanix.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Kirti Wankhede" <kwankhede@nvidia.com>,
qemu-devel@nongnu.org,
"Alex Williamson" <alex.williamson@redhat.com>,
"Thanos Makatos" <thanos.makatos@nutanix.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: VFIO Migration
Date: Thu, 5 Nov 2020 07:53:55 -0500 [thread overview]
Message-ID: <20201105075117-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20201105114037.GC462479@stefanha-x1.localdomain>
On Thu, Nov 05, 2020 at 11:40:37AM +0000, Stefan Hajnoczi wrote:
> On Wed, Nov 04, 2020 at 05:32:02PM +0000, Dr. David Alan Gilbert wrote:
> > * Stefan Hajnoczi (stefanha@redhat.com) wrote:
> > > Michael replied in another sub-thread wondering if versions are really
> > > necessary since tools do the migration checks. Let's try dropping
> > > versions to simplify things. We can bring them back if needed later.
> >
> > What does a user facing tool do? If I say I want one of these NICs
> > and I'm on the latest QEMU machine type, who sets all these parameters?
>
> The machine type is orthogonal since QEMU doesn't know about every
> possible VFIO device. The device is like a PCI adapter that is added to
> a physical machine aftermarket, it's not part of the base machine's
> specs.
I think at least at the first stage, it is a smart thing to do
to have a list of allowed devices in QEMU. This way we can ask
for a spec of the migration format, include it in qemu
(or a subtree? I don't mind ...) and check it is sane.
And we can be reasonably sure we can make changes
without breaking the world - we will know whom to
contact if we change the protocol.
--
MST
next prev parent reply other threads:[~2020-11-05 12:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 11:11 VFIO Migration Stefan Hajnoczi
2020-11-02 12:28 ` Cornelia Huck
2020-11-02 14:56 ` Stefan Hajnoczi
2020-11-04 8:07 ` Gerd Hoffmann
2020-11-04 16:40 ` Stefan Hajnoczi
2020-11-05 6:47 ` Gerd Hoffmann
2020-11-05 11:42 ` Stefan Hajnoczi
2020-11-02 19:38 ` Alex Williamson
2020-11-03 11:03 ` Stefan Hajnoczi
2020-11-03 17:13 ` Alex Williamson
2020-11-03 18:09 ` Stefan Hajnoczi
2020-11-05 23:37 ` Yan Zhao
2020-11-03 8:46 ` Jason Wang
2020-11-03 12:15 ` Stefan Hajnoczi
2020-11-04 3:32 ` Jason Wang
2020-11-04 7:16 ` Stefan Hajnoczi
2020-11-03 11:39 ` Daniel P. Berrangé
2020-11-03 15:05 ` Stefan Hajnoczi
2020-11-03 15:23 ` Daniel P. Berrangé
2020-11-03 18:16 ` Stefan Hajnoczi
2020-11-03 12:17 ` Dr. David Alan Gilbert
2020-11-03 15:27 ` Stefan Hajnoczi
2020-11-03 18:49 ` Dr. David Alan Gilbert
2020-11-04 7:36 ` Stefan Hajnoczi
2020-11-04 10:14 ` Dr. David Alan Gilbert
2020-11-04 16:47 ` Stefan Hajnoczi
2020-11-04 17:32 ` Dr. David Alan Gilbert
2020-11-05 11:40 ` Stefan Hajnoczi
2020-11-05 12:13 ` Dr. David Alan Gilbert
2020-11-05 12:47 ` Michael S. Tsirkin
2020-11-05 14:17 ` Dr. David Alan Gilbert
2020-11-05 12:53 ` Michael S. Tsirkin [this message]
2020-11-04 11:05 ` Christophe de Dinechin
2020-11-03 15:23 ` Christophe de Dinechin
2020-11-03 15:33 ` Daniel P. Berrangé
2020-11-03 17:31 ` Alex Williamson
2020-11-04 10:13 ` Stefan Hajnoczi
2020-11-04 11:10 ` Stefan Hajnoczi
2020-11-04 7:50 ` Michael S. Tsirkin
2020-11-04 16:37 ` Stefan Hajnoczi
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=20201105075117-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=felipe@nutanix.com \
--cc=jasowang@redhat.com \
--cc=john.g.johnson@oracle.com \
--cc=kwankhede@nvidia.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
--cc=thanos.makatos@nutanix.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).