summaryrefslogtreecommitdiffstats
path: root/drivers/misc/hpilo.c
diff options
context:
space:
mode:
authorIan Munsie <imunsie@au1.ibm.com>2016-05-24 02:14:05 +1000
committerMichael Ellerman <mpe@ellerman.id.au>2016-06-16 23:08:49 +1000
commit292841b09648ce7aee5df16ab72581f3b6c2bd7a (patch)
tree1da803196a927f5c4ecc54cb9d6724c0ece274bf /drivers/misc/hpilo.c
parent64417a398973d964139306c0b152536e468bf77c (diff)
downloadop-kernel-dev-292841b09648ce7aee5df16ab72581f3b6c2bd7a.zip
op-kernel-dev-292841b09648ce7aee5df16ab72581f3b6c2bd7a.tar.gz
cxl: Update process element after allocating interrupts
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> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'drivers/misc/hpilo.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud