[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB5276CF0833BF362C1BE5F2268CB0A@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Thu, 16 Nov 2023 03:19:13 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>,
Joerg Roedel <joro@...tes.org>,
"Will Deacon" <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
"Jason Gunthorpe" <jgg@...pe.ca>
CC: "iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/4] iommu/vt-d: Introduce dev_to_iommu()
> From: Lu Baolu <baolu.lu@...ux.intel.com>
> Sent: Thursday, November 16, 2023 9:51 AM
>
> +static inline struct intel_iommu *dev_to_iommu(struct device *dev)
> +{
> + /*
> + * Assume that valid per-device iommu structure must be installed
> + * if iommu_probe_device() has succeeded. This helper could only
> + * be used after device is probed.
> + */
> + return ((struct device_domain_info *)dev_iommu_priv_get(dev))-
> >iommu;
> +}
Not sure whether this helper is useful. This is only used by 2 out of 5
post-probe users. Probably just open-coding in all 5 places is clearer.
Powered by blists - more mailing lists