From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: linuxppc-dev@lists.ozlabs.org
Cc: "Jose Ricardo Ziviani" <joserz@linux.ibm.com>,
"Alexey Kardashevskiy" <aik@ozlabs.ru>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
kvm-ppc@vger.kernel.org,
"Piotr Jaroszynski" <pjaroszynski@nvidia.com>,
"Leonardo Augusto Guimarães Garcia" <lagarcia@br.ibm.com>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: [PATCH kernel RFC 0/2] vfio, powerpc/powernv: Isolate GV100GL
Date: Fri, 15 Mar 2019 19:18:33 +1100 [thread overview]
Message-ID: <20190315081835.14083-1-aik@ozlabs.ru> (raw)
Here is an attempt to isolate NVLink interconnects between GPU to
let them be passed through individually.
At the moment I mostly wonder about the sanity of the appoach.
Please comment. Thanks.
Alexey Kardashevskiy (2):
vfio_pci: Allow device specific error handlers
vfio-pci-nvlink2: Implement interconnect isolation
drivers/vfio/pci/vfio_pci_private.h | 5 ++
arch/powerpc/platforms/powernv/npu-dma.c | 24 +++++-
drivers/vfio/pci/vfio_pci.c | 17 ++++
drivers/vfio/pci/vfio_pci_nvlink2.c | 98 ++++++++++++++++++++++++
4 files changed, 142 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2019-03-15 8:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 8:18 Alexey Kardashevskiy [this message]
2019-03-15 8:18 ` [PATCH kernel RFC 1/2] vfio_pci: Allow device specific error handlers Alexey Kardashevskiy
2019-03-15 8:18 ` [PATCH kernel RFC 2/2] vfio-pci-nvlink2: Implement interconnect isolation Alexey Kardashevskiy
2019-03-19 16:36 ` Alex Williamson
2019-03-20 1:57 ` Alexey Kardashevskiy
2019-03-20 4:38 ` David Gibson
2019-03-20 19:09 ` Alex Williamson
2019-03-20 23:56 ` David Gibson
2019-03-21 18:19 ` Alex Williamson
2019-03-22 3:08 ` David Gibson
2019-03-22 23:10 ` Alex Williamson
2019-04-05 0:34 ` David Gibson
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=20190315081835.14083-1-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=joserz@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=lagarcia@br.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=pjaroszynski@nvidia.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).