From: christophe lombard <clombard@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, fbarrat@linux.vnet.ibm.com,
ajd@linux.ibm.com
Subject: [PATCH 0/2] ocxl: Move SPA and TL definitions
Date: Wed, 9 Oct 2019 17:11:07 +0200 [thread overview]
Message-ID: <20191009151109.13752-1-clombard@linux.vnet.ibm.com> (raw)
This series moves the definition and the management of scheduled process area
(SPA) and of the templates (Transaction Layer) for an ocxl card, using the
OCAPI interface. The code is now located in the specific arch powerpc platform.
These patches will help for a futur implementation of the ocxl driver in QEMU.
The Open Coherently Attached Processor Interface (OCAPI) is used to
allow an Attached Functional Unit (AFU) to connect to the Processor
Chip's system bus in a high speed and cache coherent manner.
It builds on top of the existing ocxl driver.
It has been tested in a bare-metal environment using the memcpy and
the AFP AFUs.
christophe lombard (2):
powerpc/powernv: ocxl move SPA definition
powerpc/powernv: ocxl move TL definition
arch/powerpc/include/asm/pnv-ocxl.h | 30 +-
arch/powerpc/platforms/powernv/ocxl.c | 378 +++++++++++++++++++++++---
drivers/misc/ocxl/afu_irq.c | 1 -
drivers/misc/ocxl/config.c | 89 +-----
drivers/misc/ocxl/link.c | 347 +++++++----------------
drivers/misc/ocxl/ocxl_internal.h | 12 -
drivers/misc/ocxl/trace.h | 34 +--
7 files changed, 467 insertions(+), 424 deletions(-)
--
2.21.0
next reply other threads:[~2019-10-09 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 15:11 christophe lombard [this message]
2019-10-09 15:11 ` [PATCH 1/2] powerpc/powernv: ocxl move SPA definition christophe lombard
2019-10-14 10:17 ` Frederic Barrat
2019-10-14 14:00 ` christophe lombard
2019-10-09 15:11 ` [PATCH 2/2] powerpc/powernv: ocxl move TL definition christophe lombard
2019-10-14 10:21 ` Frederic Barrat
2019-10-14 15:32 ` christophe lombard
2019-10-09 22:19 ` [PATCH 0/2] ocxl: Move SPA and TL definitions Daniel Axtens
2019-10-10 22:34 ` Andrew Donnellan
2019-10-11 8:06 ` christophe lombard
2019-10-11 9:10 ` christophe lombard
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=20191009151109.13752-1-clombard@linux.vnet.ibm.com \
--to=clombard@linux.vnet.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.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).