kernel-packages team mailing list archive

[Vaibhav <vaibhav@xxxxxxxxxxxxxxxxxx>]

Hi Canonical,

We have successfully verified this fix in xenial-proposed kernel. So
tagging this bug as 'verification-done-xenial'


** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1588468

Title:
  CAPI: CGZIP AFU contexts do not receive interrupts after heavy afu
  open/close

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - Breno Henrique Leitao <brenohl@xxxxxxxxxx> - 2016-06-02 13:36:27 ==
  ---Problem Description---
  We are developing a CAPI version of our FPGA gzip compression adapter. We use AFU directed mode to support multiple processes. Our testcase is opening a huge number of AFU context and sending small work-requests to the card. After n sec we close the AFU contexts.

  What we observe is that after a while we get a set of AFU contexts,
  which do not see interrupts anymore. We have traced the interrupt
  packet (msix I guess) to the very low level of the FPGA logic and we
  strongly assume that the interrupt packet goes out. Still the Linux
  kernel is not seeing the interrupt and our application times out but
  the work request was successfully finished.

  In order to fix this bug, the follow patches are required:

  2bc79ffcbb817873cc43d63118008ab75181b73d cxl: Poll for outstanding IRQs when detaching a context
  d6776bba44d9752f6cdf640046070e71ee4bba7b cxl: Keep IRQ mappings on context teardown
   
  This request is for Ubuntu 16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1588468/+subscriptions