From: Alex Williamson <alex.williamson@redhat.com>
To: alex.williamson@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, clg@redhat.com
Subject: [PATCH 0/2] vfio/mtty: Add migration support
Date: Fri, 13 Oct 2023 13:56:51 -0600 [thread overview]
Message-ID: <20231013195653.1222141-1-alex.williamson@redhat.com> (raw)
We've seen a request for CI and development to have access to migratable
vfio devices without any specific hardware requirements. One way to do
that is to enable migration support on the mtty mdev sample driver, as
done here.
This device is particularly easy to migrate because it doesn't actually
do DMA, or in fact much of anything. Therefore we can claim P2P and
dirty logging as well. PRE_COPY support is also included in a similar
fashion to hisi_acc. This provides early compatibility testing, which
is probably over-done, but perhaps illustrates good practice with
matching data stream magic, versioning, and feature flags. These might
later be used for backwards compatibility, particularly since I'm not
positive that copying the struct serial_port between source and
destination is sufficient.
Along the way, testing migration where the source and target are
incompatible, I fixed an eventfd leak. Thanks,
Alex
Alex Williamson (2):
vfio/mtty: Fix eventfd leak
vfio/mtty: Enable migration support
samples/vfio-mdev/mtty.c | 610 ++++++++++++++++++++++++++++++++++++++-
1 file changed, 605 insertions(+), 5 deletions(-)
--
2.40.1
next reply other threads:[~2023-10-13 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 19:56 Alex Williamson [this message]
2023-10-13 19:56 ` [PATCH 1/2] vfio/mtty: Fix eventfd leak Alex Williamson
2023-10-16 7:52 ` Cédric Le Goater
2023-10-16 20:16 ` Alex Williamson
2023-10-13 19:56 ` [PATCH 2/2] vfio/mtty: Enable migration support Alex Williamson
2023-10-16 14:29 ` Cédric Le Goater
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=20231013195653.1222141-1-alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®