From: Michael Ellerman <mpe@ellerman•id.au>
To: Ian Munsie <imunsie@au1•ibm.com>, mikey <mikey@neuling•org>,
linuxppc-dev@lists•ozlabs.org,
Frederic Barrat <frederic.barrat@fr•ibm.com>,
Huy Nguyen <huyn@mellanox•com>
Cc: Ian Munsie <imunsie@au1•ibm.com>
Subject: Re: cxl: Update process element after allocating interrupts
Date: Tue, 21 Jun 2016 10:40:53 +1000 (AEST) [thread overview]
Message-ID: <3rYTRT2Cxyz9t18@ozlabs.org> (raw)
In-Reply-To: <1464020045-1385-1-git-send-email-imunsie@au.ibm.com>
On Mon, 2016-23-05 at 16:14:05 UTC, Ian Munsie wrote:
> From: Ian Munsie <imunsie@au1•ibm.com>
>
> In the kernel API, it is possible to attempt to allocate AFU interrupts
> after already starting a context. Since the process element structure
> used by the hardware is only filled out at the time the context is
> started, it will not be updated with the interrupt numbers that have
> just been allocated and therefore AFU interrupts will not work unless
> they were allocated prior to starting the context.
>
> This can present some difficulties as each CAPI enabled PCI device in
> the kernel API has a default context, which may need to be started very
> early to enable translations, potentially before interrupts can easily
> be set up.
>
> This patch makes the API more flexible to allow interrupts to be
> allocated after a context has already been started and takes care of
> updating the PE structure used by the hardware and notifying it to
> discard any cached copy it may have.
>
> The update is currently performed via a terminate/remove/add sequence.
> This is necessary on some hardware such as the XSL that does not
> properly support the update LLCMD.
>
> Note that this is only supported on powernv at present - attempting to
> perform this ordering on PowerVM will raise a warning.
>
> Signed-off-by: Ian Munsie <imunsie@au1•ibm.com>
> Reviewed-by: Frederic Barrat <fbarrat@linux•vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/292841b09648ce7aee5df16ab7
cheers
prev parent reply other threads:[~2016-06-21 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 16:14 [PATCH] cxl: Update process element after allocating interrupts Ian Munsie
2016-05-24 11:25 ` Frederic Barrat
2016-06-21 0:40 ` Michael Ellerman [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=3rYTRT2Cxyz9t18@ozlabs.org \
--to=mpe@ellerman$(echo .)id.au \
--cc=frederic.barrat@fr$(echo .)ibm.com \
--cc=huyn@mellanox$(echo .)com \
--cc=imunsie@au1$(echo .)ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mikey@neuling$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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