From: Marc Zyngier <maz@kernel.org>
To: John Garry <john.garry@huawei.com>,
Andrew Murray <andrew.murray@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Bjorn Helgaas <bhelgaas@google.com>,
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: Thu, 5 Sep 2019 11:02:10 +0100 [thread overview]
Message-ID: <651b4d5f-2d86-65dc-1232-580445852752@kernel.org> (raw)
In-Reply-To: <84f6756f-79f2-2e46-fe44-9a46be69f99d@huawei.com>
On 05/09/2019 10:39, John Garry wrote:
>>
>> That's a "feature" of the architecture. The ITT is sized by the number
>> of bits used to index the table, meaning that you can only describe a
>> power of two >= 2.
>>
>> John, could you stick a "#define DEBUG 1" at the top of irq-gic-v3-its.c
>> and report the LPI allocations for this device?
>>
>
> Hi Marc,
>
> As requested, I enabled debug for that driver and here are some kernel
> log snippets:
>
> [ 8.435707] hisi_sas_v3_hw 0000:74:02.0: Adding to iommu group 0
> [ 8.461467] scsi host0: hisi_sas_v3_hw
> [ 9.683463] ITS: alloc 9920:32
> [ 9.686509] ITT 32 entries, 5 bits
> [ 9.690044] ID:0 pID:9920 vID:23
> [ 9.693263] ID:1 pID:9921 vID:24
> [ 9.696480] ID:2 pID:9922 vID:25
> [ 9.699696] ID:3 pID:9923 vID:26
> [ 9.702911] ID:4 pID:9924 vID:27
> [ 9.706128] ID:5 pID:9925 vID:28
> [ 9.709344] ID:6 pID:9926 vID:29
> [ 9.712560] ID:7 pID:9927 vID:30
> [ 9.715776] ID:8 pID:9928 vID:31
> [ 9.718990] ID:9 pID:9929 vID:32
> [ 9.722207] ID:10 pID:9930 vID:33
> [ 9.725510] ID:11 pID:9931 vID:34
> [ 9.728813] ID:12 pID:9932 vID:35
> [ 9.732116] ID:13 pID:9933 vID:36
> [ 9.735419] ID:14 pID:9934 vID:37
> [ 9.738721] ID:15 pID:9935 vID:38
> [ 9.742024] ID:16 pID:9936 vID:39
>
> <snip>
>
> (none)$ echo 0000:74:02.0 > ./sys/bus/pci/drivers/hisi_sas_v3_hw/unbind
>
> <snip>
>
> root@(none)$
> $ echo 0000:74:02.0 > ./sys/bus/pci/drivers/hisi_sas_v3_hw/bind
> [ 41.110557] scsi host0: hisi_sas_v3_hw
> [ 42.335455] Reusing ITT for devID 7410
> [ 42.359151] hisi_sas_v3_hw: probe of 0000:74:02.0 failed with error -2
> sh: echo: write error: No such device
> root@(none)$
Very interesting. Somehow, we think that this is a *new* device that
aliases with itself. Needless to say, that's unexpected. My hunch is
that something goes wrong when freeing the device. Can you try adding
the patch below and report what is happening on unbind?
Thanks,
M.
diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
index 1b5c3672aea2..3fed87e551d9 100644
--- a/drivers/irqchip/irq-gic-v3-its.c
+++ b/drivers/irqchip/irq-gic-v3-its.c
@@ -2651,6 +2651,8 @@ static void its_irq_domain_free(struct irq_domain *domain, unsigned int virq,
/* Nuke the entry in the domain */
irq_domain_reset_irq_data(data);
+
+ pr_debug("Freed devid %x LPI %ld\n", its_dev->device_id, data->hwirq);
}
mutex_lock(&its->dev_alloc_lock);
@@ -2667,6 +2669,7 @@ static void its_irq_domain_free(struct irq_domain *domain, unsigned int virq,
its_dev->event_map.nr_lpis);
kfree(its_dev->event_map.col_map);
+ pr_debug("Unmap devid %x\n", its_dev->device_id);
/* Unmap device/itt */
its_send_mapd(its_dev, 0);
its_free_device(its_dev);
--
Jazz is not dead, it just smells funny...
next prev parent reply other threads:[~2019-09-05 10:02 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
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 [this message]
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=651b4d5f-2d86-65dc-1232-580445852752@kernel.org \
--to=maz@kernel.org \
--cc=andrew.murray@arm.com \
--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®