From: Alistair Popple <alistair@popple.id.au>
To: linuxppc-dev@ozlabs.org
Cc: gwshan@linux.vnet.ibm.com, benh@kernel.crashing.org,
Alistair Popple <alistair@popple.id.au>
Subject: [PATCH 0/2] Add support for Nvlink
Date: Wed, 28 Oct 2015 16:00:00 +1100 [thread overview]
Message-ID: <1446008402-24892-1-git-send-email-alistair@popple.id.au> (raw)
This series adds support for Nvlink, a high speed interconnect that is
used in conjunction with PCI-E to create a high bandwidth interface
between GPU and CPU.
As the Nvlink hardware interface is similar to IBM's existing PCIe
host bridges no major new kernel or user interfaces are added by this
patch series. Instead the links are treated as standard PCIe devices
sitting under a Nvlink specific PHB type. This allows existing kernel
interfaces to be used for the management and control of the links.
Alistair Popple (2):
Revert "powerpc/pci: Remove unused struct pci_dn.pcidev field"
platforms/powernv: Add support for Nvlink NPUs
arch/powerpc/include/asm/pci-bridge.h | 1 +
arch/powerpc/include/asm/pci.h | 4 +
arch/powerpc/platforms/powernv/Makefile | 2 +-
arch/powerpc/platforms/powernv/npu-dma.c | 267 ++++++++++++++++++++++++++++++
arch/powerpc/platforms/powernv/pci-ioda.c | 105 ++++++++++--
arch/powerpc/platforms/powernv/pci.c | 4 +
arch/powerpc/platforms/powernv/pci.h | 10 ++
7 files changed, 381 insertions(+), 12 deletions(-)
create mode 100644 arch/powerpc/platforms/powernv/npu-dma.c
--
2.1.4
next reply other threads:[~2015-10-28 5:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 5:00 Alistair Popple [this message]
2015-10-28 5:00 ` [PATCH 1/2] Revert "powerpc/pci: Remove unused struct pci_dn.pcidev field" Alistair Popple
2015-10-28 5:00 ` [PATCH 2/2] platforms/powernv: Add support for Nvlink NPUs Alistair Popple
2015-11-10 2:28 ` [PATCH v2] " Alistair Popple
2015-11-10 8:51 ` kbuild test robot
2015-11-10 10:30 ` Michael Ellerman
2015-11-10 10:43 ` kbuild test robot
2015-12-14 9:26 ` [v2] " Michael Ellerman
2015-12-15 2:46 ` Alistair Popple
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=1446008402-24892-1-git-send-email-alistair@popple.id.au \
--to=alistair@popple.id.au \
--cc=benh@kernel.crashing.org \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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).