public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	lorenzo.pieralisi@arm.com, Thomas Gleixner <tglx@linutronix.de>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	Vidya Sagar <vidyas@nvidia.com>
Subject: Re: [RFC] PCI/MSI: Warning observed for NVMe with ACPI
Date: Fri, 10 Dec 2021 12:25:13 +0000	[thread overview]
Message-ID: <5b3f3544-b7a5-c338-d53a-c6d7ff3ac8e0@nvidia.com> (raw)
In-Reply-To: <874k7g1yf2.wl-maz@kernel.org>

Hi Marc,

On 10/12/2021 11:39, Marc Zyngier wrote:

...

>> So the question is, should this be enabled by default for ARM64? I see
>> a lot of other architectures enabling this when PCI_MSI is enabled. So
>> I am wondering if we should be doing something like ...
>>
>> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
>> index 1f212b47a48a..4bbd81bab809 100644
>> --- a/arch/arm64/Kconfig
>> +++ b/arch/arm64/Kconfig
>> @@ -202,6 +202,7 @@ config ARM64
>>          select PCI_DOMAINS_GENERIC if PCI
>>          select PCI_ECAM if (ACPI && PCI)
>>          select PCI_SYSCALL if PCI
>> +       select PCI_MSI_ARCH_FALLBACKS if PCI_MSI
>>          select POWER_RESET
>>          select POWER_SUPPLY
>>          select SPARSE_IRQ
> 
> +Thomas, as he's neck-deep in the MSI rework.
> 
> No, this definitely is the wrong solution.
> 
> arm64 doesn't need any arch fallback (I actually went out of my way to
> kill them on this architecture), and requires the individual MSI
> controller drivers to do the right thing by using MSI domains.  Adding
> this config option makes the warning disappear, but the core issue is
> that you have a device that doesn't have a MSI domain associated with
> it.
> 
> So either your device isn't MSI capable (odd), your host bridge
> doesn't make the link with the MSI controller to advertise the MSI
> domain (this should normally be dealt with via IORT), or there is a
> bug of a similar sort somewhere else.
> 
> Getting to the root of this issue would be the right thing to do.


Thanks! I will chat with Sagar about this and see what we are missing.

Jon

-- 
nvpublic

  reply	other threads:[~2021-12-10 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 10:48 [RFC] PCI/MSI: Warning observed for NVMe with ACPI Jon Hunter
2021-12-10 11:39 ` Marc Zyngier
2021-12-10 12:25   ` Jon Hunter [this message]
2021-12-11  9:50   ` Thomas Gleixner

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=5b3f3544-b7a5-c338-d53a-c6d7ff3ac8e0@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vidyas@nvidia.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