[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250221145141.GA291164@nvidia.com>
Date: Fri, 21 Feb 2025 10:51:41 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Nicolin Chen <nicolinc@...dia.com>
Cc: kevin.tian@...el.com, tglx@...utronix.de, maz@...nel.org,
joro@...tes.org, will@...nel.org, robin.murphy@....com,
shuah@...nel.org, iommu@...ts.linux.dev,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kselftest@...r.kernel.org, eric.auger@...hat.com,
baolu.lu@...ux.intel.com, yi.l.liu@...el.com, yury.norov@...il.com,
jacob.pan@...ux.microsoft.com, patches@...ts.linux.dev
Subject: Re: [PATCH v2 6/7] iommufd: Implement sw_msi support natively
On Wed, Feb 19, 2025 at 05:31:41PM -0800, Nicolin Chen wrote:
> +/*
> + * Get a iommufd_sw_msi_map for the msi physical address requested by the irq
> + * layer. The mapping to IOVA is global to the iommufd file descriptor, every
> + * domain that is attached to a device using the same MSI parameters will use
> + * the same IOVA.
> + */
> +static struct iommufd_sw_msi_map *
> +iommufd_sw_msi_get_map(struct iommufd_ctx *ictx, phys_addr_t msi_addr,
> + phys_addr_t sw_msi_start)
> +{
This ends up being never called if !CONFIG_IRQ_MSI_IOMMU because the
sw_msi doesn't exist.
--- a/drivers/iommu/iommufd/device.c
+++ b/drivers/iommu/iommufd/device.c
@@ -300,7 +300,7 @@ EXPORT_SYMBOL_NS_GPL(iommufd_device_to_id, "IOMMUFD");
* domain that is attached to a device using the same MSI parameters will use
* the same IOVA.
*/
-static struct iommufd_sw_msi_map *
+static __maybe_unused struct iommufd_sw_msi_map *
iommufd_sw_msi_get_map(struct iommufd_ctx *ictx, phys_addr_t msi_addr,
phys_addr_t sw_msi_start)
{
Fixed it up
Jason
Powered by blists - more mailing lists