From: Naman Jain <namjain@linux.microsoft.com>
To: 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>,
Shradha Gupta <shradhagupta@linux.microsoft.com>
Cc: Naman Jain <namjain@linux.microsoft.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org,
Roman Kisel <romank@linux.microsoft.com>
Subject: [PATCH] PCI/MSI: Initialize the prepare descriptor by default
Date: Tue, 8 Jul 2025 10:48:48 +0530 [thread overview]
Message-ID: <20250708051848.3214-1-namjain@linux.microsoft.com> (raw)
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
next reply other threads:[~2025-07-08 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 5:18 Naman Jain [this message]
2025-07-08 10:02 ` [PATCH] PCI/MSI: Initialize the prepare descriptor by default Shradha Gupta
2025-07-08 10:15 ` Naman Jain
2025-07-08 16:08 ` Bjorn Helgaas
2025-07-09 4:42 ` Naman Jain
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=20250708051848.3214-1-namjain@linux.microsoft.com \
--to=namjain@linux.microsoft.com \
--cc=bhelgaas@google.com \
--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 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.