From: Baolu Lu <baolu.lu@linux.intel.com>
To: Vasant Hegde <vasant.hegde@amd.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] iommu: Make iommu_sva_domain_alloc() static
Date: Fri, 31 May 2024 08:59:13 +0800 [thread overview]
Message-ID: <cb8f4a3f-75f4-436a-96dc-301b6d65a55c@linux.intel.com> (raw)
In-Reply-To: <fdc3bffa-7149-48a4-949a-dd469c6c2726@amd.com>
On 5/30/24 4:52 PM, Vasant Hegde wrote:
> On 5/28/2024 10:24 AM, Lu Baolu wrote:
>> iommu_sva_domain_alloc() is only called in iommu-sva.c, hence make it
>> static.
>>
>> On the other hand, iommu_sva_domain_alloc() should not return NULL anymore
>> after commit <80af5a452024> ("iommu: Add ops->domain_alloc_sva()"), the
>> removal of inline code avoids potential confusion.
>>
>> Fixes: 80af5a452024 ("iommu: Add ops->domain_alloc_sva()")
>> Signed-off-by: Lu Baolu<baolu.lu@linux.intel.com>
>> ---
>> include/linux/iommu.h | 8 --------
>> drivers/iommu/iommu-sva.c | 6 ++++--
>> 2 files changed, 4 insertions(+), 10 deletions(-)
>>
>> diff --git a/include/linux/iommu.h b/include/linux/iommu.h
>> index 7bc8dff7cf6d..5cdd3d41b87b 100644
>> --- a/include/linux/iommu.h
>> +++ b/include/linux/iommu.h
>> @@ -1527,8 +1527,6 @@ struct iommu_sva *iommu_sva_bind_device(struct device *dev,
>> struct mm_struct *mm);
>> void iommu_sva_unbind_device(struct iommu_sva *handle);
>> u32 iommu_sva_get_pasid(struct iommu_sva *handle);
>> -struct iommu_domain *iommu_sva_domain_alloc(struct device *dev,
>> - struct mm_struct *mm);
>> #else
>> static inline struct iommu_sva *
>> iommu_sva_bind_device(struct device *dev, struct mm_struct *mm)
>> @@ -1553,12 +1551,6 @@ static inline u32 mm_get_enqcmd_pasid(struct mm_struct *mm)
>> }
>>
>> static inline void mm_pasid_drop(struct mm_struct *mm) {}
>> -
>> -static inline struct iommu_domain *
>> -iommu_sva_domain_alloc(struct device *dev, struct mm_struct *mm)
>> -{
>> - return NULL;
>> -}
>> #endif /* CONFIG_IOMMU_SVA */
>>
>> #ifdef CONFIG_IOMMU_IOPF
>> diff --git a/drivers/iommu/iommu-sva.c b/drivers/iommu/iommu-sva.c
>> index 18a35e798b72..25e581299226 100644
>> --- a/drivers/iommu/iommu-sva.c
>> +++ b/drivers/iommu/iommu-sva.c
>> @@ -10,6 +10,8 @@
>> #include "iommu-priv.h"
>>
>> static DEFINE_MUTEX(iommu_sva_lock);
>> +static struct iommu_domain *iommu_sva_domain_alloc(struct device *dev,
>> + struct mm_struct *mm);
> If we move move iommu_sva_domain_alloc() before iommu_sva_bind_device() then we
> can avoid this forward declaration.
Yeah, but that means moving 144 lines of code. That's why I went with
this approach
Best regards,
baolu
next prev parent reply other threads:[~2024-05-31 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 4:54 Lu Baolu
2024-05-29 2:27 ` Tian, Kevin
2024-05-30 8:52 ` Vasant Hegde
2024-05-31 0:59 ` Baolu Lu [this message]
2024-05-31 6:09 ` Vasant Hegde
2024-06-10 17:31 ` Jason Gunthorpe
2024-06-13 9:15 ` Joerg Roedel
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=cb8f4a3f-75f4-436a-96dc-301b6d65a55c@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=vasant.hegde@amd.com \
--cc=will@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
Powered by JetHome