From: John Garry <john.garry@huawei.com>
To: Luo Jiaxing <luojiaxing@huawei.com>, <maz@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linuxarm@openeuler.org>
Subject: Re: [Linuxarm] [PATCH v1 0/2] irqchip/gic-v3-its: don't set bitmap for LPI which user didn't allocate
Date: Mon, 8 Feb 2021 11:14:19 +0000 [thread overview]
Message-ID: <ea730f9b-c635-317d-c70d-4057590b1d1a@huawei.com> (raw)
In-Reply-To: <1612781926-56206-1-git-send-email-luojiaxing@huawei.com>
On 08/02/2021 10:58, Luo Jiaxing wrote:
> When the number of online CPUs is less than 16, we found that it will fail
> to allocate 32 MSI interrupts (including 16 affinity interrupts) after the
> hisi_sas module is unloaded and then reloaded.
>
> After analysis, it is found that a bug exists when the ITS releases
> interrupt resources, and this patch set contains a bugfix patch and a patch
> for appending debugging information.
Please note that this issue has already been reported:
https://lore.kernel.org/lkml/fd88ce05-8aee-5b1f-5ab6-be88fa53d3aa@huawei.com/
>
> Luo Jiaxing (2):
> irqchip/gic-v3-its: don't set bitmap for LPI which user didn't
> allocate
> genirq/msi: add an error print when __irq_domain_alloc_irqs() failed
>
> drivers/irqchip/irq-gic-v3-its.c | 4 ++++
> kernel/irq/msi.c | 1 +
> 2 files changed, 5 insertions(+)
>
prev parent reply other threads:[~2021-02-08 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 10:58 [PATCH v1 0/2] irqchip/gic-v3-its: don't set bitmap for LPI which user didn't allocate Luo Jiaxing
2021-02-08 10:58 ` [PATCH v1 1/2] " Luo Jiaxing
2021-02-08 11:59 ` Marc Zyngier
2021-02-09 7:25 ` luojiaxing
2021-02-08 10:58 ` [PATCH v1 2/2] genirq/msi: add an error print when __irq_domain_alloc_irqs() failed Luo Jiaxing
2021-02-08 11:14 ` John Garry [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=ea730f9b-c635-317d-c70d-4057590b1d1a@huawei.com \
--to=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=luojiaxing@huawei.com \
--cc=maz@kernel.org \
/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).