From: Jagannathan Raman <jag.raman@oracle.com>
To: qemu-devel@nongnu.org
Cc: elena.ufimtseva@oracle.com, john.g.johnson@oracle.com,
thuth@redhat.com, jag.raman@oracle.com,
swapnil.ingle@nutanix.com, john.levon@nutanix.com,
philmd@redhat.com, alex.williamson@redhat.com,
marcandre.lureau@gmail.com, stefanha@redhat.com,
thanos.makatos@nutanix.com, pbonzini@redhat.com,
alex.bennee@linaro.org
Subject: [PATCH v3 00/12] vfio-user server in QEMU
Date: Mon, 11 Oct 2021 01:31:05 -0400 [thread overview]
Message-ID: <cover.1633929457.git.jag.raman@oracle.com> (raw)
Based-on: <cover.1629131628.git.elena.ufimtseva@oracle.com>
Hi,
Thank you very much for reviewing the patches in the previous revision!
We have addressed most of comments from v2.
We are working on MSI-x support (used by PCIe devices such as “nvme”)
and a couple of comments in the migration patches. We hope these two
items will be in the next revision of the patches.
Please the list below for changes since last revision:
[PATCH RFC v3 01/12] configure, meson: override C compiler for cmake
- New patch in this rev
[PATCH RFC v3 02/12] vfio-user: build library
- fixed indentation issue
- dropped separate MAINTAINERS section for submodule. using
existing section to avoid checkpatch warning
[PATCH RFC v3 03/12] vfio-user: define vfio-user-server object
- Changed socket parameter type to SocketAddress from str
- renamed object as vfio-user-server
- renamed devid option as device
- Added CONFIG_VFIO_USER_SERVER option
[PATCH RFC v3 04/12] vfio-user: instantiate vfio-user context
- removed errno.h include
- documented reason for using a machine init done notifier
- don’t call vfu_destroy_ctx() if context is not initialized
[PATCH RFC v3 05/12] vfio-user: find and init PCI device
- registering for PCI Express devices as well. Tested with
“nvme” device in QEMU.
- MSI-x is not supported yet, PCI-e devices using INTx
presently. Will add a patch shortly to address MSI-x
[PATCH RFC v3 06/12] vfio-user: run vfio-user context
- Removed the separate QemuThread for attach as it was blocking
- Using qemu_set_fd_handler() for attach’ing context
[PATCH RFC v3 07/12] vfio-user: handle PCI config space accesses
- Using pci_host_config_read_common/write/common() instead of pci_default_read/write_config()
- The read_common/write_common() should take care of endianness
[PATCH RFC v3 09/12] vfio-user: handle PCI BAR accesses
- Added support for 64-bit BARs
[PATCH RFC v3 11/12] vfio-user: register handlers to facilitate migration
- Fixed size handling in vfu_mig_buf_read()
- Moved qemu_remote_savevm() from “precopy” phase to “stop_and_copy”
- Opening “vfu_mig_file” just before use
- TODO: Working with Nutanix on issues concerning the “resume”
phase and size of Migration BAR (the size of migration BAR shouldn’t
matter when using vfu_migration_callbacks_t).
Please share your comments.
Thank you!
Jagannathan Raman (12):
configure, meson: override C compiler for cmake
vfio-user: build library
vfio-user: define vfio-user-server object
vfio-user: instantiate vfio-user context
vfio-user: find and init PCI device
vfio-user: run vfio-user context
vfio-user: handle PCI config space accesses
vfio-user: handle DMA mappings
vfio-user: handle PCI BAR accesses
vfio-user: handle device interrupts
vfio-user: register handlers to facilitate migration
vfio-user: acceptance test
configure | 15 +-
meson.build | 39 +
qapi/qom.json | 20 +-
include/hw/remote/iohub.h | 2 +
migration/savevm.h | 2 +
hw/remote/iohub.c | 5 +
hw/remote/vfio-user-obj.c | 868 +++++++++++++++++++++
migration/savevm.c | 73 ++
.gitlab-ci.d/buildtest.yml | 2 +
.gitmodules | 3 +
MAINTAINERS | 3 +
hw/remote/Kconfig | 5 +
hw/remote/meson.build | 3 +
hw/remote/trace-events | 11 +
subprojects/libvfio-user | 1 +
tests/acceptance/multiprocess.py | 2 +
tests/acceptance/vfio-user.py | 96 +++
tests/docker/dockerfiles/centos8.docker | 2 +
tests/docker/dockerfiles/ubuntu2004.docker | 2 +
19 files changed, 1151 insertions(+), 3 deletions(-)
create mode 100644 hw/remote/vfio-user-obj.c
create mode 160000 subprojects/libvfio-user
create mode 100644 tests/acceptance/vfio-user.py
--
2.20.1
next reply other threads:[~2021-10-11 5:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 5:31 Jagannathan Raman [this message]
2021-10-11 5:31 ` [PATCH v3 01/12] configure, meson: override C compiler for cmake Jagannathan Raman
2021-10-12 10:44 ` Paolo Bonzini
2021-10-11 5:31 ` [PATCH v3 02/12] vfio-user: build library Jagannathan Raman
2021-10-27 15:17 ` Stefan Hajnoczi
2021-10-29 14:17 ` Jag Raman
2021-11-01 9:56 ` Stefan Hajnoczi
2021-10-11 5:31 ` [PATCH v3 03/12] vfio-user: define vfio-user-server object Jagannathan Raman
2021-10-27 15:40 ` Stefan Hajnoczi
2021-10-29 14:42 ` Jag Raman
2021-11-01 10:34 ` Stefan Hajnoczi
2021-11-04 12:13 ` Markus Armbruster
2021-11-04 14:39 ` Kevin Wolf
2021-11-05 10:08 ` Markus Armbruster
2021-11-05 13:19 ` Kevin Wolf
2021-11-05 13:54 ` Peter Krempa
2021-11-06 6:34 ` Markus Armbruster
2021-11-08 12:05 ` Kevin Wolf
2021-11-08 12:54 ` Peter Krempa
2021-11-04 16:48 ` Stefan Hajnoczi
2021-10-11 5:31 ` [PATCH v3 04/12] vfio-user: instantiate vfio-user context Jagannathan Raman
2021-10-27 15:59 ` Stefan Hajnoczi
2021-10-29 14:59 ` Jag Raman
2021-11-01 10:35 ` Stefan Hajnoczi
2021-10-11 5:31 ` [PATCH v3 05/12] vfio-user: find and init PCI device Jagannathan Raman
2021-10-27 16:05 ` Stefan Hajnoczi
2021-10-29 15:58 ` Jag Raman
2021-11-01 10:38 ` Stefan Hajnoczi
2021-10-11 5:31 ` [PATCH v3 06/12] vfio-user: run vfio-user context Jagannathan Raman
2021-10-27 16:21 ` Stefan Hajnoczi
2021-10-28 21:55 ` John Levon
2021-10-11 5:31 ` [PATCH v3 07/12] vfio-user: handle PCI config space accesses Jagannathan Raman
2021-10-27 16:35 ` Stefan Hajnoczi
2021-10-11 5:31 ` [PATCH v3 08/12] vfio-user: handle DMA mappings Jagannathan Raman
2021-10-11 5:31 ` [PATCH v3 09/12] vfio-user: handle PCI BAR accesses Jagannathan Raman
2021-10-27 16:38 ` Stefan Hajnoczi
2021-10-11 5:31 ` [PATCH v3 10/12] vfio-user: handle device interrupts Jagannathan Raman
2021-10-11 5:31 ` [PATCH v3 11/12] vfio-user: register handlers to facilitate migration Jagannathan Raman
2021-10-27 18:30 ` Stefan Hajnoczi
2021-12-15 15:49 ` Jag Raman
2021-10-11 5:31 ` [PATCH v3 12/12] vfio-user: acceptance test Jagannathan Raman
2021-10-11 22:26 ` Philippe Mathieu-Daudé
2021-10-27 16:42 ` Stefan Hajnoczi
2021-10-27 18:33 ` [PATCH v3 00/12] vfio-user server in QEMU 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=cover.1633929457.git.jag.raman@oracle.com \
--to=jag.raman@oracle.com \
--cc=alex.bennee@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=john.levon@nutanix.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=swapnil.ingle@nutanix.com \
--cc=thanos.makatos@nutanix.com \
--cc=thuth@redhat.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).