From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: a175818323@gmail.com
Subject: [Qemu-devel] [PATCH 0/3] vfio/pci: Add NVIDIA GPUDirect P2P clique support
Date: Tue, 29 Aug 2017 16:05:24 -0600 [thread overview]
Message-ID: <20170829214929.31136.21144.stgit@gimli.home> (raw)
NVIDIA has a specification for exposing a virtual vendor capability
which provides a hint to guest drivers as to which sets of GPUs can
support direct peer-to-peer DMA. Devices with the same clique ID are
expected to support this. The user can specify a clique ID for an
NVIDIA graphics device using the new vfio-pci x-nv-gpudirect-clique=
option, where valid clique IDs are a 4-bit integer. It's entirely the
user's responsibility to specify sets of devices for which P2P works
correctly and provides some benefit. This is only useful for DMA
between NVIDIA GPUs, therefore it's only useful to specify cliques
comprised of more than one GPU. Furthermore, this does not enable DMA
between VMs, there is no change to VM DMA mapping, this only exposes
hints about existing DMA paths to the guest driver. Thanks,
Alex
---
Alex Williamson (3):
vfio/pci: Do not unwind on error
vfio/pci: Add virtual capabilities quirk infrastructure
vfio/pci: Add NVIDIA GPUDirect Cliques support
hw/vfio/pci-quirks.c | 114 ++++++++++++++++++++++++++++++++++++++++++++++++++
hw/vfio/pci.c | 17 +++++++
hw/vfio/pci.h | 4 ++
3 files changed, 133 insertions(+), 2 deletions(-)
next reply other threads:[~2017-08-29 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 22:05 Alex Williamson [this message]
2017-08-29 22:05 ` [Qemu-devel] [PATCH 1/3] vfio/pci: Do not unwind on error Alex Williamson
2017-08-29 22:05 ` [Qemu-devel] [PATCH 2/3] vfio/pci: Add virtual capabilities quirk infrastructure Alex Williamson
2017-08-29 22:05 ` [Qemu-devel] [PATCH 3/3] vfio/pci: Add NVIDIA GPUDirect Cliques support Alex Williamson
2017-10-26 10:45 ` [Qemu-devel] [PATCH 0/3] vfio/pci: Add NVIDIA GPUDirect P2P clique support Bob Chen
2017-11-20 10:45 ` Bob Chen
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=20170829214929.31136.21144.stgit@gimli.home \
--to=alex.williamson@redhat.com \
--cc=a175818323@gmail.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).