From: Marc Zyngier <maz@kernel.org>
To: John Garry <john.garry@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>,
"luojiaxing@huawei.com" <luojiaxing@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PCI/kernel msi code vs GIC ITS driver conflict?
Date: Tue, 3 Sep 2019 17:16:16 +0100 [thread overview]
Message-ID: <5fd4c1cf-76c1-4054-3754-549317509310@kernel.org> (raw)
In-Reply-To: <f5e948aa-e32f-3f74-ae30-31fee06c2a74@huawei.com>
Hi John,
On 03/09/2019 15:09, John Garry wrote:
> Hi Marc, Bjorn, Thomas,
>
> We've come across a conflict with the kernel/pci msi code and GIC ITS
> driver on our arm64 system, whereby we can't unbind and re-bind a PCI
> device driver under special conditions. I'll explain...
>
> Our PCI device support 32 MSIs. The driver attempts to allocate msi
> vectors with min msi=17, max msi = 32, and affd.pre vectors = 16. For
> our test we make nr_cpus = 1 (just anything less than 16).
Just to confirm: this PCI device is requiring Multi-MSI, right? As
opposed to MSI-X?
> We find that the pci/kernel msi code gives us 17 vectors, but the GIC
> ITS code reserves 32 lpi maps in its_irq_domain_alloc(). The problem
> then occurs when unbinding the driver in its_irq_domain_free() call,
> where we only clear bits for 17 vectors. So if we unbind the driver and
> then attempt to bind again, it fails.
Is this device, by any chance, sharing its requested-id with another
device? By being behind a bridge of some sort? There is some code to
deal with it, but I'm not sure it has ever been verified in anger...
> Where the fault lies, I can't say. Maybe the kernel msi code should
> always give power of 2 vectors - as I understand, the PCI spec mandates
> this. Or maybe the GIC ITS driver has a problem in the free path, as
> above. Or maybe the PCI driver should not be allowed to request !power
> of 2 min/max vectors.
>
> Opinion?
My hunch is that it is an ITS driver bug: the PCI layer is allowed to
give any number of MSIs to an endpoint driver, as long as they match the
requirements of the allocation for Multi-MSI. That's the responsibility
of the ITS driver. If unbind/bind fails, it means that somehow we've
missed the freeing of the LPIs, which isn't good.
Is the device common enough that I can try and reproduce the issue? If
there's a Linux driver somewhere, I can always hack something in
emulation and find out...
Thanks,
M.
--
Jazz is not dead, it just smells funny...
next prev parent reply other threads:[~2019-09-03 16:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 14:09 John Garry
2019-09-03 16:16 ` Marc Zyngier [this message]
2019-09-04 8:56 ` John Garry
2019-09-04 10:25 ` Andrew Murray
2019-09-05 8:38 ` Marc Zyngier
2019-09-05 9:39 ` John Garry
2019-09-05 10:02 ` Marc Zyngier
2019-09-05 10:35 ` John Garry
2019-09-05 11:22 ` Marc Zyngier
2019-09-05 13:26 ` John Garry
2019-09-05 13:50 ` Marc Zyngier
2019-09-05 14:23 ` John Garry
2019-09-05 14:32 ` Marc Zyngier
2019-09-05 14:53 ` John Garry
2019-09-05 15:09 ` Marc Zyngier
2019-09-06 11:08 ` [tip: irq/core] irqchip/gic-v3-its: Fix LPI release for Multi-MSI devices tip-bot2 for Marc Zyngier
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=5fd4c1cf-76c1-4054-3754-549317509310@kernel.org \
--to=maz@kernel.org \
--cc=bhelgaas@google.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=luojiaxing@huawei.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®