From: John Garry <john.garry@huawei.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
chenxiang <chenxiang66@hisilicon.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"liuqi (BA)" <liuqi115@huawei.com>
Subject: Re: PCI MSI issue for maxcpus=1
Date: Fri, 7 Jan 2022 11:24:38 +0000 [thread overview]
Message-ID: <19d55cdf-9ef7-e4a3-5ae5-0970f0d7751b@huawei.com> (raw)
In-Reply-To: <87a6g8vp8k.wl-maz@kernel.org>
Hi Marc,
>> So it's the driver call to pci_alloc_irq_vectors_affinity() which
>> errors [1]:
>>
>> [ 9.619070] hisi_sas_v3_hw: probe of 0000:74:02.0 failed with error -2
> Can you log what error is returned from pci_alloc_irq_vectors_affinity()?
-EINVAL
>
>> Some details:
>> - device supports 32 MSI
>> - min and max msi for that function is 17 and 32, respect.
> This 17 is a bit odd, owing to the fact that MultiMSI can only deal
> with powers of 2. You will always allocate 32 in this case. Not sure
> why that'd cause an issue though. Unless...
Even though 17 is the min, we still try for nvec=32 in
msi_capability_init() as possible CPUs is 96.
>
>> - affd pre and post are 16 and 0, respect.
>>
>> I haven't checked to see what the issue is yet and I think that the
>> pci_alloc_irq_vectors_affinity() usage is ok...
> ... we really end-up with desc->nvec_used == 32 and try to activate
> past vector 17 (which is likely to fail). Could you please check this?
Yeah, that looks to fail. Reason being that in the GIC ITS driver when
we try to activate the irq for this managed interrupt all cpus in the
affinity mask are offline. Calling its_irq_domain_activate() ->
its_select_cpu() it gives cpu=nr_cpu_ids. The affinity mask for that
interrupt is 24-29.
Thanks,
John
next prev parent reply other threads:[~2022-01-07 11:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 11:23 John Garry
2022-01-06 15:49 ` Marc Zyngier
2022-01-07 11:24 ` John Garry [this message]
2022-01-16 12:07 ` Marc Zyngier
2022-01-17 9:14 ` Marc Zyngier
2022-01-17 11:59 ` John Garry
2022-01-24 11:22 ` Marc Zyngier
2022-03-04 12:53 ` John Garry
2022-03-05 15:40 ` Marc Zyngier
2022-03-07 13:48 ` John Garry
2022-03-07 14:01 ` Marc Zyngier
2022-03-07 14:03 ` Marc Zyngier
2022-03-08 1:37 ` David Decotigny
2022-03-08 3:57 ` Xiongfeng Wang
[not found] ` <87zgm0zfw7.wl-maz@kernel.org>
2022-03-10 3:19 ` Xiongfeng Wang
[not found] ` <87o82eyxmz.wl-maz@kernel.org>
2022-03-10 12:58 ` Xiongfeng Wang
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=19d55cdf-9ef7-e4a3-5ae5-0970f0d7751b@huawei.com \
--to=john.garry@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuqi115@huawei.com \
--cc=maz@kernel.org \
--cc=shameerali.kolothum.thodi@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®