From: Xiubo Li <xiubli@redhat.com>
To: "Harris, James R" <james.r.harris@intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jiang, Dave" <dave.jiang@intel.com>,
"Walker, Benjamin" <benjamin.walker@intel.com>,
"Wodkowski, PawelX" <pawelx.wodkowski@intel.com>
Subject: Re: Problems with uio_pci_generic in v4.18-rc8
Date: Sun, 12 Aug 2018 18:55:58 +0800 [thread overview]
Message-ID: <7ac09d84-31bf-4d25-dba7-0a61effa2b04@redhat.com> (raw)
In-Reply-To: <21BF98B1-0EA5-46BC-BC68-196190880087@intel.com>
Hi Harris,
Since the lock protection in uio irq handler is useless currently as
discussed in the mail list, so I will revert this commit with small
changes and now the testing based LIO/TCMU has been finished.
Thanks,
BRs
On 2018/8/11 5:12, Harris, James R wrote:
> Hi,
>
> Using Linux kernel v4.18-rc8, I am unable to bind a PCI device to uio_pci_generic. This works fine with v4.18-rc4. dmesg shows:
>
> [ 336.221585] genirq: Threaded irq requested with handler=NULL and !ONESHOT for irq 33
> [ 336.221681] uio_pci_generic: probe of 0000:04:00.0 failed with error -22
>
> This problem has been reproduced on multiple systems.
>
> This seems to be related to commit 9421e45f5 (“uio: use request_threaded_irq instead”) which was merged in -rc5. Reverting this commit fixes the issue (I also reverted 543af5861f and 57c5f4df0a which also touch uio.c - just to be safe).
>
> This seems like a serious regression to uio_pci_generic, but any tips or pointers would be appreciated.
>
> Thanks,
>
> Jim Harris
>
next prev parent reply other threads:[~2018-08-12 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 21:12 Problems with uio_pci_generic in v4.18-rc8 Harris, James R
2018-08-12 10:55 ` Xiubo Li [this message]
2018-08-12 11:03 ` gregkh
2018-08-12 11:45 ` Xiubo Li
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=7ac09d84-31bf-4d25-dba7-0a61effa2b04@redhat.com \
--to=xiubli@redhat.com \
--cc=benjamin.walker@intel.com \
--cc=dave.jiang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=james.r.harris@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pawelx.wodkowski@intel.com \
/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).