From: Christoph Hellwig <hch@infradead.org>
To: Kirti Wankhede <kwankhede@nvidia.com>
Cc: alex.williamson@redhat.com, cjia@nvidia.com,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC PATCH v1 1/4] VFIO KABI for migration interface
Date: Wed, 17 Oct 2018 02:06:21 -0700 [thread overview]
Message-ID: <20181017090621.GB19942@infradead.org> (raw)
In-Reply-To: <1539713558-2453-2-git-send-email-kwankhede@nvidia.com>
On Tue, Oct 16, 2018 at 11:42:35PM +0530, Kirti Wankhede wrote:
> - Added vfio_device_migration_info structure to use interact with vendor
> driver.
There is no such thing as a 'vendor driver' in Linux - all drivers ate
treated equal. And I don't see any single driver supporting this yet,
so you really should submit your noveau or whatever patches first.
next prev parent reply other threads:[~2018-10-17 9:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 18:12 [Qemu-devel] [RFC PATCH v1 0/4] Add migration support for VFIO device Kirti Wankhede
2018-10-16 18:12 ` [Qemu-devel] [RFC PATCH v1 1/4] VFIO KABI for migration interface Kirti Wankhede
2018-10-16 22:34 ` Alex Williamson
2018-10-17 20:47 ` Kirti Wankhede
2018-10-17 23:14 ` Alex Williamson
2018-10-18 1:49 ` Gonglei (Arei)
2018-10-17 9:06 ` Christoph Hellwig [this message]
2018-10-17 10:09 ` Dr. David Alan Gilbert
2018-10-17 21:17 ` Kirti Wankhede
2018-10-18 9:23 ` Dr. David Alan Gilbert
2018-10-16 18:12 ` [Qemu-devel] [RFC PATCH v1 2/4] Add migration functions for VFIO devices Kirti Wankhede
2018-10-17 9:00 ` Cornelia Huck
2018-10-17 21:03 ` Kirti Wankhede
2018-10-16 18:12 ` [Qemu-devel] [RFC PATCH v1 3/4] Add vfio_listerner_log_sync to mark dirty pages Kirti Wankhede
2018-10-16 18:12 ` [Qemu-devel] [RFC PATCH v1 4/4] Make vfio-pci device migration capable Kirti Wankhede
2018-10-17 8:49 ` [Qemu-devel] [RFC PATCH v1 0/4] Add migration support for VFIO device Cornelia Huck
2018-10-17 20:59 ` Kirti Wankhede
2018-10-18 2:41 ` Tian, Kevin
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=20181017090621.GB19942@infradead.org \
--to=hch@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=cjia@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.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).