From: christophe lombard <clombard@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, fbarrat@linux.vnet.ibm.com,
ajd@linux.ibm.com, groug@kaod.org
Subject: [PATCH V2 0/2] ocxl: Move SPA and TL definitions
Date: Wed, 16 Oct 2019 17:59:11 +0200 [thread overview]
Message-ID: <20191016155913.13693-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.
The Scheduled Processes Area and the configuration of the Transaction
Layer are specific to the AFU and more generally to the Opencapi device.
Running the ocxl module in a guest environment, and later in several guests
in parallel, using the same Opencapi device and the same AFus, involves to
have a common code handling the SPA. This explains why these parts of the ocxl
driver will move to arch powerpc platform running on the host.
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.
Changelog:
v2:
- patch 1: delete debug message as it no longer makes sense. (Fred)
Rename pnv_ocxl_read_xsl_regs to pnv_ocxl_get_fault_state. (Fred)
Rename pnv_ocxl_write_xsl_tfc to pnv_ocxl_handle_fault. (Fred)
Call opal_npu_spa_clear_cache() internally without using external
function. (Fred)
Remove pe_handle parameter from pnv_ocxl_update_pe() (Fred)
Not possible to split this patch in 2 (one part for the SPA
handling, the other for the translation fault interrupt). There are
far too many dependencies with the SPA structure. (Fred)
Switch the order of the pe_data allocation and the call to add the
entry in the SPA. (Fred)
christophe lombard (2):
powerpc/powernv: ocxl move SPA definition
powerpc/powernv: ocxl move TL definition
arch/powerpc/include/asm/pnv-ocxl.h | 46 +--
arch/powerpc/platforms/powernv/ocxl.c | 400 +++++++++++++++++++++++---
drivers/misc/ocxl/afu_irq.c | 1 -
drivers/misc/ocxl/config.c | 89 +-----
drivers/misc/ocxl/link.c | 383 ++++++------------------
drivers/misc/ocxl/ocxl_internal.h | 12 -
drivers/misc/ocxl/trace.h | 64 ++---
7 files changed, 508 insertions(+), 487 deletions(-)
--
2.21.0
next reply other threads:[~2019-10-16 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 15:59 christophe lombard [this message]
2019-10-16 15:59 ` [PATCH V2 1/2] powerpc/powernv: ocxl move SPA definition christophe lombard
2019-10-16 15:59 ` [PATCH V2 2/2] powerpc/powernv: ocxl move TL definition 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=20191016155913.13693-1-clombard@linux.vnet.ibm.com \
--to=clombard@linux.vnet.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=groug@kaod.org \
--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).