From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jason Andryuk <jason.andryuk@amd.com>
Cc: xen-devel@lists.xenproject.org, Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Anthony PERARD <anthony.perard@vates.tech>,
Michal Orzel <michal.orzel@amd.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Xenia Ragiadakou <xenia.ragiadakou@amd.com>
Subject: Re: [RFC PATCH] xen/amd-iommu: Add interrupt remapping quirk for ath11k
Date: Thu, 13 Mar 2025 16:47:40 +0100 [thread overview]
Message-ID: <Z9L-HPlfZhvIh8yn@macbook.local> (raw)
In-Reply-To: <1d3ac61a-1acf-46b3-91bc-1dcb8bab1559@amd.com>
On Thu, Mar 13, 2025 at 11:30:28AM -0400, Jason Andryuk wrote:
> On 2025-02-27 05:23, Roger Pau Monné wrote:
> > On Wed, Feb 26, 2025 at 04:11:25PM -0500, Jason Andryuk wrote:
> > >
> > > The ath11k device supports and tries to enable 32 MSIs. Linux in PVH
> > > dom0 and HVM domU fails enabling 32 and falls back to just 1, so that is
> > > all that has been tested.
> >
> > DYK why it fails to enable 32?
>
> In Linux msi_capability_init()
>
> /* Reject multi-MSI early on irq domain enabled architectures */
> if (nvec > 1 && !pci_msi_domain_supports(dev,
> MSI_FLAG_MULTI_PCI_MSI, ALLOW_LEGACY))
> return 1;
>
> MSI_FLAG_MULTI_PCI_MSI is only set for AMD and Intel interrupt remapping,
> and Xen PVH and HVM don't have either of those. They are using "VECTOR", so
> this check fails.
Oh, interesting. So classic PV MSI domain supports
MSI_FLAG_MULTI_PCI_MSI, even when no IOMMU is exposed there either.
Thanks, so it's nothing specific to Xen, just how Linux works.
Roger.
next prev parent reply other threads:[~2025-03-13 15:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 21:11 [RFC PATCH] xen/amd-iommu: Add interrupt remapping quirk for ath11k Jason Andryuk
2025-02-27 8:54 ` Jan Beulich
2025-02-27 16:49 ` Jason Andryuk
2025-03-05 8:09 ` Jan Beulich
2025-02-27 10:23 ` Roger Pau Monné
2025-02-27 18:28 ` Jason Andryuk
2025-02-27 19:00 ` Andrew Cooper
2025-02-28 9:36 ` Roger Pau Monné
2025-02-28 20:25 ` Jason Andryuk
2025-03-04 10:23 ` Roger Pau Monné
2025-03-04 15:15 ` Jason Andryuk
2025-03-04 16:41 ` Roger Pau Monné
2025-03-05 8:41 ` Jan Beulich
2025-03-13 15:30 ` Jason Andryuk
2025-03-13 15:47 ` Roger Pau Monné [this message]
2025-03-13 16:02 ` Andrew Cooper
2025-03-13 16:07 ` Jan Beulich
2025-03-13 16:24 ` Andrew Cooper
2025-03-13 18:03 ` Jason Andryuk
2025-02-27 11:14 ` Andrew Cooper
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=Z9L-HPlfZhvIh8yn@macbook.local \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jason.andryuk@amd.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xenia.ragiadakou@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.