From: Russell Currey <ruscur@russell.cc>
To: Frederic Barrat <fbarrat@linux.vnet.ibm.com>,
mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
mikey@neuling.org, benh@kernel.crashing.org,
brking@linux.vnet.ibm.com, clsoto@linux.vnet.ibm.com
Subject: Re: [PATCH v4] powerpc/powernv: Enable PCI peer-to-peer
Date: Mon, 07 Aug 2017 16:30:39 +1000 [thread overview]
Message-ID: <1502087439.8488.4.camel@russell.cc> (raw)
In-Reply-To: <20170804095514.11224-1-fbarrat@linux.vnet.ibm.com>
On Fri, 2017-08-04 at 11:55 +0200, Frederic Barrat wrote:
> P9 has support for PCI peer-to-peer, enabling a device to write in the
> mmio space of another device directly, without interrupting the CPU.
>
> This patch adds support for it on powernv, by adding a new API to be
> called by drivers. The pnv_pci_set_p2p(...) call configures an
> 'initiator', i.e the device which will issue the mmio operation, and a
> 'target', i.e. the device on the receiving side.
>
> P9 really only supports mmio stores for the time being but that's
> expected to change in the future, so the API allows to define both
> load and store operations.
>
> /* PCI p2p descriptor */
> #define OPAL_PCI_P2P_ENABLE 0x1
> #define OPAL_PCI_P2P_LOAD 0x2
> #define OPAL_PCI_P2P_STORE 0x4
>
> int pnv_pci_set_p2p(struct pci_dev *initiator, struct pci_dev *target,
> uint64_t desc)
>
> It uses a new OPAL call, as the configuration magic is done on the
> PHBs by skiboot.
>
> Signed-off-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
> ---
Reviewed-by: Russell Currey <ruscur@russell.cc>
next prev parent reply other threads:[~2017-08-07 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 9:55 [PATCH v4] powerpc/powernv: Enable PCI peer-to-peer Frederic Barrat
2017-08-07 6:30 ` Russell Currey [this message]
2017-08-07 6:59 ` Michael Ellerman
2017-08-08 10:55 ` [v4] " Michael Ellerman
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=1502087439.8488.4.camel@russell.cc \
--to=ruscur@russell.cc \
--cc=benh@kernel.crashing.org \
--cc=brking@linux.vnet.ibm.com \
--cc=clsoto@linux.vnet.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
/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).