From: Naman Jain <namjain@linux.microsoft.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Shradha Gupta <shradhagupta@linux.microsoft.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Shivamurthy Shastri <shivamurthy.shastri@linutronix.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org,
Roman Kisel <romank@linux.microsoft.com>
Subject: Re: [PATCH] PCI/MSI: Initialize the prepare descriptor by default
Date: Wed, 9 Jul 2025 10:12:09 +0530 [thread overview]
Message-ID: <34d1f7e4-0729-4faf-95b7-e2fce6c3be2e@linux.microsoft.com> (raw)
In-Reply-To: <20250708160817.GA2148355@bhelgaas>
On 7/8/2025 9:38 PM, Bjorn Helgaas wrote:
> On Tue, Jul 08, 2025 at 03:45:05PM +0530, Naman Jain wrote:
>> On 7/8/2025 3:32 PM, Shradha Gupta wrote:
>>> On Tue, Jul 08, 2025 at 10:48:48AM +0530, Naman Jain wrote:
>>>> Plug the default MSI-X prepare descriptor for non-implemented ops by
>>>> default to workaround the inability of Hyper-V vPCI module to setup
>>>> the MSI-X descriptors properly; especially for dynamically allocated
>>>> MSI-X.
>>>>
>>>> Signed-off-by: Naman Jain <namjain@linux.microsoft.com>
>>>> ---
>>>> drivers/pci/msi/irqdomain.c | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/drivers/pci/msi/irqdomain.c b/drivers/pci/msi/irqdomain.c
>>>> index 765312c92d9b..655e99b9c8cc 100644
>>>> --- a/drivers/pci/msi/irqdomain.c
>>>> +++ b/drivers/pci/msi/irqdomain.c
>>>> @@ -84,6 +84,8 @@ static void pci_msi_domain_update_dom_ops(struct msi_domain_info *info)
>>>> } else {
>>>> if (ops->set_desc == NULL)
>>>> ops->set_desc = pci_msi_domain_set_desc;
>>>> + if (ops->prepare_desc == NULL)
>>>> + ops->prepare_desc = pci_msix_prepare_desc;
>>>> }
>>>> }
>>>>
>>>> base-commit: 26ffb3d6f02cd0935fb9fa3db897767beee1cb2a
>>>> --
>>>> 2.34.1
>>>>
>>>
>>> Hey Naman,
>>>
>>> can you please try your tests with this patch:
>>> https://lore.kernel.org/all/1749651015-9668-1-git-send-email-shradhagupta@linux.microsoft.com/
>>> I think this should help your use case
>>
>> Hey,
>> Thanks for sharing this, this works for me.
>>
>> Closing this thread.
>
> I guess this means we should ignore this patch? If it turns out that
> we do need this patch, I'd like to add some details in the commit log
> about what this problem looks like to users.
>
> Bjorn
Yes, my patch is no longer required, since it was doing the same thing
that Shradha's patch (1-2) were doing, but in a different way. Shradha's
patch is better and would suffice for the use case. Please ignore this
patch.
Thanks.
Regards,
Naman
prev parent reply other threads:[~2025-07-09 4:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 5:18 Naman Jain
2025-07-08 10:02 ` Shradha Gupta
2025-07-08 10:15 ` Naman Jain
2025-07-08 16:08 ` Bjorn Helgaas
2025-07-09 4:42 ` Naman Jain [this message]
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=34d1f7e4-0729-4faf-95b7-e2fce6c3be2e@linux.microsoft.com \
--to=namjain@linux.microsoft.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=romank@linux.microsoft.com \
--cc=shivamurthy.shastri@linutronix.de \
--cc=shradhagupta@linux.microsoft.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®