From: christophe lombard <clombard@linux.vnet.ibm.com>
To: Andrew Donnellan <ajd@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, fbarrat@linux.vnet.ibm.com
Subject: Re: [PATCH 0/2] ocxl: Move SPA and TL definitions
Date: Fri, 11 Oct 2019 11:10:01 +0200 [thread overview]
Message-ID: <791d02d6-cf9c-b2da-59a5-669d14451780@linux.vnet.ibm.com> (raw)
In-Reply-To: <f15fbc65-c14f-a75d-92b0-8f7619dfda36@linux.vnet.ibm.com>
On 11/10/2019 10:06, christophe lombard wrote:
> On 11/10/2019 00:34, Andrew Donnellan wrote:
>> On 10/10/19 2:11 am, christophe lombard wrote:
>>> 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.
>>
>> Could you explain more about this?
>>
>
> 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.
>
> Thanks.
>
Implementation of the ocxl driver running on a QEMU guest environment
will be detailed in the following patches but basically, a new ocxl vfio
driver, running in the host, will interact, in side, with the SPA, using
the pnv_ api(s) and on the other hand will interact, through ioctl
commands, with the guest(s). Ocxl, running in the guest, through hcalls
(handled by QEMU) will configure the device and interact with the vfio
through ioctl commands.
>
>>
>> Andrew
>>
>>
>>>
>>> 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(-)
>>>
>>
>
prev parent reply other threads:[~2019-10-11 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 15:11 [PATCH 0/2] ocxl: Move SPA and TL definitions christophe lombard
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 [this message]
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=791d02d6-cf9c-b2da-59a5-669d14451780@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).