From: Dave Jiang <dave.jiang@intel.com>
To: Dan Williams <dan.j.williams@intel.com>, linux-cxl@vger.kernel.org
Cc: kernel test robot <lkp@intel.com>,
Julia Lawall <julia.lawall@lip6.fr>,
Davidlohr Bueso <dave@stgolabs.net>,
Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH] cxl/pci: Fix irq oneshot expectations
Date: Tue, 31 Jan 2023 08:21:45 -0700 [thread overview]
Message-ID: <6e3ae578-52bd-baeb-1957-ecfaf655973c@intel.com> (raw)
In-Reply-To: <167512370284.2509057.12212781340425308386.stgit@dwillia2-xfh.jf.intel.com>
On 1/30/23 5:08 PM, Dan Williams wrote:
> The IRQ core expects that users of the default hardirq handler specify
> IRQF_ONESHOT to keep interrupts disabled until the threaded handler
> runs. That meets the CXL driver's expectations since it is an edge
> triggered MSI and this flag would have been passed by default using
> pci_request_irq() instead of devm_request_threaded_irq().
>
> Fixes: a49aa8141b65 ("cxl/mem: Wire up event interrupts")
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Julia Lawall <julia.lawall@lip6.fr>
> Cc: Davidlohr Bueso <dave@stgolabs.net>
> Cc: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/cxl/pci.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cxl/pci.c b/drivers/cxl/pci.c
> index ad2ebe7bfaeb..4cf9a2191602 100644
> --- a/drivers/cxl/pci.c
> +++ b/drivers/cxl/pci.c
> @@ -509,7 +509,8 @@ static int cxl_event_req_irq(struct cxl_dev_state *cxlds, u8 setting)
> return irq;
>
> return devm_request_threaded_irq(dev, irq, NULL, cxl_event_thread,
> - IRQF_SHARED, NULL, dev_id);
> + IRQF_SHARED | IRQF_ONESHOT, NULL,
> + dev_id);
> }
>
> static int cxl_event_get_int_policy(struct cxl_dev_state *cxlds,
>
prev parent reply other threads:[~2023-01-31 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 0:08 [PATCH] cxl/pci: Fix irq oneshot expectations Dan Williams
2023-01-31 15:21 ` Dave Jiang [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=6e3ae578-52bd-baeb-1957-ecfaf655973c@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-cxl@vger.kernel.org \
--cc=lkp@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