From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, avihaih@nvidia.com, clg@redhat.com
Subject: [PULL 00/12] VFIO updates 2023-02-16
Date: Thu, 16 Feb 2023 16:01:47 -0700 [thread overview]
Message-ID: <167658846945.932837.1420176491103357684.stgit@omen> (raw)
The following changes since commit 6dffbe36af79e26a4d23f94a9a1c1201de99c261:
Merge tag 'migration-20230215-pull-request' of https://gitlab.com/juan.quintela/qemu into staging (2023-02-16 13:09:51 +0000)
are available in the Git repository at:
https://gitlab.com/alex.williamson/qemu.git tags/vfio-updates-20230216.0
for you to fetch changes up to 57edb7e44489ec4d85075acba47223127ecf1521:
MAINTAINERS: Add myself as VFIO reviewer (2023-02-16 12:14:40 -0700)
----------------------------------------------------------------
VFIO updates 2023-02-16
* Initial v2 migration support for vfio (Avihai Horon)
* Add Cédric as vfio reviewer (Cédric Le Goater)
----------------------------------------------------------------
Avihai Horon (11):
linux-headers: Update to v6.2-rc8
vfio/migration: Fix NULL pointer dereference bug
vfio/migration: Allow migration without VFIO IOMMU dirty tracking support
vfio/common: Change vfio_devices_all_running_and_saving() logic to equivalent one
vfio/migration: Block multiple devices migration
vfio/migration: Move migration v1 logic to vfio_migration_init()
vfio/migration: Rename functions/structs related to v1 protocol
vfio/migration: Implement VFIO migration protocol v2
vfio/migration: Remove VFIO migration protocol v1
vfio: Alphabetize migration section of VFIO trace-events file
docs/devel: Align VFIO migration docs to v2 protocol
Cédric Le Goater (1):
MAINTAINERS: Add myself as VFIO reviewer
MAINTAINERS | 1 +
docs/devel/vfio-migration.rst | 72 +-
hw/vfio/common.c | 92 ++-
hw/vfio/migration.c | 736 +++++++--------------
hw/vfio/trace-events | 28 +-
include/hw/vfio/vfio-common.h | 10 +-
include/standard-headers/drm/drm_fourcc.h | 29 +
include/standard-headers/linux/ethtool.h | 18 +-
include/standard-headers/linux/fuse.h | 16 +-
include/standard-headers/linux/input-event-codes.h | 3 +
include/standard-headers/linux/pci_regs.h | 2 +
include/standard-headers/linux/virtio_bt.h | 8 +
include/standard-headers/linux/virtio_net.h | 4 +
linux-headers/asm-arm64/kvm.h | 1 +
linux-headers/asm-riscv/kvm.h | 3 +
linux-headers/asm-x86/kvm.h | 11 +-
linux-headers/linux/kvm.h | 34 +-
linux-headers/linux/psci.h | 4 +-
linux-headers/linux/vfio.h | 136 +++-
19 files changed, 612 insertions(+), 596 deletions(-)
next reply other threads:[~2023-02-16 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 23:01 Alex Williamson [this message]
2023-02-16 23:01 ` [PULL 01/12] linux-headers: Update to v6.2-rc8 Alex Williamson
2023-02-16 23:02 ` [PULL 02/12] vfio/migration: Fix NULL pointer dereference bug Alex Williamson
2023-02-16 23:02 ` [PULL 03/12] vfio/migration: Allow migration without VFIO IOMMU dirty tracking support Alex Williamson
2023-02-16 23:02 ` [PULL 04/12] vfio/common: Change vfio_devices_all_running_and_saving() logic to equivalent one Alex Williamson
2023-02-16 23:02 ` [PULL 05/12] vfio/migration: Block multiple devices migration Alex Williamson
2023-02-16 23:02 ` [PULL 06/12] vfio/migration: Move migration v1 logic to vfio_migration_init() Alex Williamson
2023-02-16 23:02 ` [PULL 07/12] vfio/migration: Rename functions/structs related to v1 protocol Alex Williamson
2023-02-16 23:02 ` [PULL 08/12] vfio/migration: Implement VFIO migration protocol v2 Alex Williamson
2023-02-16 23:02 ` [PULL 09/12] vfio/migration: Remove VFIO migration protocol v1 Alex Williamson
2023-02-16 23:02 ` [PULL 10/12] vfio: Alphabetize migration section of VFIO trace-events file Alex Williamson
2023-02-16 23:02 ` [PULL 11/12] docs/devel: Align VFIO migration docs to v2 protocol Alex Williamson
2023-02-16 23:02 ` [PULL 12/12] MAINTAINERS: Add myself as VFIO reviewer Alex Williamson
2023-02-21 11:27 ` [PULL 00/12] VFIO updates 2023-02-16 Peter Maydell
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=167658846945.932837.1420176491103357684.stgit@omen \
--to=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=clg@redhat.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).