From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
shangsong2@lenovo.com, Dave Jiang <dave.jiang@intel.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/1] iommu: Allow attaching static domains in iommu_attach_device_pasid()
Date: Thu, 24 Apr 2025 09:36:19 +0800 [thread overview]
Message-ID: <d9756d68-9d40-4fa7-8d11-5a260dc4f4cd@linux.intel.com> (raw)
In-Reply-To: <20250423142102.GL1648741@nvidia.com>
On 4/23/25 22:21, Jason Gunthorpe wrote:
> On Wed, Apr 23, 2025 at 10:18:39AM +0800, Lu Baolu wrote:
>> @@ -3435,7 +3448,8 @@ int iommu_attach_device_pasid(struct iommu_domain *domain,
>> !ops->blocked_domain->ops->set_dev_pasid)
>> return -EOPNOTSUPP;
>>
>> - if (ops != domain->owner || pasid == IOMMU_NO_PASID)
>> + if (!domain_iommu_ops_compatible(ops, domain) ||
>> + pasid == IOMMU_NO_PASID)
>> return -EINVAL;
> Convert all the places checking domain->owner to the new function..
>
> static int __iommu_attach_group(struct iommu_domain *domain,
> struct iommu_group *group)
>
> int iommu_replace_device_pasid(struct iommu_domain *domain,
> struct device *dev, ioasid_t pasid,
> struct iommu_attach_handle *handle)
Sure. Will make it in a new version.
Thanks,
baolu
next prev parent reply other threads:[~2025-04-24 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 2:18 [PATCH v2 1/1] iommu: Allow attaching static domains in iommu_attach_device_pasid() Lu Baolu
2025-04-23 2:52 ` Dave Jiang
2025-04-23 14:21 ` Jason Gunthorpe
2025-04-24 1:36 ` Baolu Lu [this message]
2025-04-23 19:38 ` Robin Murphy
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=d9756d68-9d40-4fa7-8d11-5a260dc4f4cd@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=shangsong2@lenovo.com \
--cc=stable@vger.kernel.org \
--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