From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: <kys@microsoft.com>, <haiyangz@microsoft.com>,
<sthemmin@microsoft.com>, <wei.liu@kernel.org>,
<decui@microsoft.com>, <lorenzo.pieralisi@arm.com>,
<robh@kernel.org>, <kw@linux.com>, <bhelgaas@google.com>,
<jakeo@microsoft.com>
Cc: <bjorn.andersson@linaro.org>, <linux-hyperv@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] PCI: hv: Fix multi-MSI to allow more than one MSI vector
Date: Wed, 20 Apr 2022 08:13:22 -0600 [thread overview]
Message-ID: <2100eed4-8081-6070-beaf-7c6ba65ad9be@quicinc.com> (raw)
In-Reply-To: <1649856981-14649-1-git-send-email-quic_jhugo@quicinc.com>
On 4/13/2022 7:36 AM, Jeffrey Hugo wrote:
> If the allocation of multiple MSI vectors for multi-MSI fails in the core
> PCI framework, the framework will retry the allocation as a single MSI
> vector, assuming that meets the min_vecs specified by the requesting
> driver.
>
> Hyper-V advertises that multi-MSI is supported, but reuses the VECTOR
> domain to implement that for x86. The VECTOR domain does not support
> multi-MSI, so the alloc will always fail and fallback to a single MSI
> allocation.
>
> In short, Hyper-V advertises a capability it does not implement.
>
> Hyper-V can support multi-MSI because it coordinates with the hypervisor
> to map the MSIs in the IOMMU's interrupt remapper, which is something the
> VECTOR domain does not have. Therefore the fix is simple - copy what the
> x86 IOMMU drivers (AMD/Intel-IR) do by removing
> X86_IRQ_ALLOC_CONTIGUOUS_VECTORS after calling the VECTOR domain's
> pci_msi_prepare().
>
> Fixes: 4daace0d8ce8 ("PCI: hv: Add paravirtual PCI front-end for Microsoft Hyper-V VMs")
> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> Reviewed-by: Dexuan Cui <decui@microsoft.com>
> ---
Ping?
I don't see this in -next, nor have I seen any replies. It is possible
I have missed some kind of update, but currently I'm wondering if this
change is progressing or not. If there is some kind of process used in
this area, I'm not familiar with it, so I would appreciate an introduction.
Thanks
-Jeff
next prev parent reply other threads:[~2022-04-20 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 13:36 [PATCH v2] PCI: hv: Fix multi-MSI to allow more than one MSI vector Jeffrey Hugo
2022-04-20 14:13 ` Jeffrey Hugo [this message]
2022-04-25 15:33 ` Wei Liu
2022-04-25 15:49 ` Wei Liu
2022-04-25 16:52 ` Jeffrey Hugo
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=2100eed4-8081-6070-beaf-7c6ba65ad9be@quicinc.com \
--to=quic_jhugo@quicinc.com \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jakeo@microsoft.com \
--cc=kw@linux.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).