public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Yi Liu <yi.l.liu@intel.com>
To: Baolu Lu <baolu.lu@linux.intel.com>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Vasant Hegde <vasant.hegde@amd.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	"joro@8bytes.org" <joro@8bytes.org>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"robin.murphy@arm.com" <robin.murphy@arm.com>,
	"eric.auger@redhat.com" <eric.auger@redhat.com>,
	"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"chao.p.peng@linux.intel.com" <chao.p.peng@linux.intel.com>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	"Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v3 1/7] iommu: Introduce a replace API for device pasid
Date: Fri, 6 Sep 2024 13:57:47 +0800	[thread overview]
Message-ID: <6871e983-ae3a-42c8-ac63-570ba422df7e@intel.com> (raw)
In-Reply-To: <456e9b67-aa20-4259-b8e1-9f20d4fa03af@linux.intel.com>

On 2024/9/6 12:33, Baolu Lu wrote:
> On 9/6/24 12:21 PM, Yi Liu wrote:
>> On 2024/8/16 21:02, Jason Gunthorpe wrote:
>>> On Fri, Aug 16, 2024 at 05:43:18PM +0800, Yi Liu wrote:
>>>> On 2024/7/18 16:27, Tian, Kevin wrote:
>>>>>> From: Liu, Yi L <yi.l.liu@intel.com>
>>>>>> Sent: Friday, June 28, 2024 5:06 PM
>>>>>>
>>>>>> @@ -3289,7 +3290,20 @@ static int __iommu_set_group_pasid(struct
>>>>>> iommu_domain *domain,
>>>>>>
>>>>>>            if (device == last_gdev)
>>>>>>                break;
>>>>>> -        ops->remove_dev_pasid(device->dev, pasid, domain);
>>>>>> +        /* If no old domain, undo the succeeded devices/pasid */
>>>>>> +        if (!old) {
>>>>>> +            ops->remove_dev_pasid(device->dev, pasid, domain);
>>>>>> +            continue;
>>>>>> +        }
>>>>>> +
>>>>>> +        /*
>>>>>> +         * Rollback the succeeded devices/pasid to the old domain.
>>>>>> +         * And it is a driver bug to fail attaching with a previously
>>>>>> +         * good domain.
>>>>>> +         */
>>>>>> +        if (WARN_ON(old->ops->set_dev_pasid(old, device->dev,
>>>>>> +                            pasid, domain)))
>>>>>> +            ops->remove_dev_pasid(device->dev, pasid, domain);
>>>>>
>>>>> I wonder whether @remove_dev_pasid() can be replaced by having
>>>>> blocking_domain support @set_dev_pasid?
>>>>
>>>> how about your thought, @Jason?
>>>
>>> I think we talked about doing that once before, I forget why it was
>>> not done. Maybe there was an issue?
>>>
>>> But it seems worth trying.
>>
>> Since remove_dev_pasid() does not return a result, so caller does not
>> need to check the result of it. If we want to replace it with the
>> blocked_domain->ops->set_dev_pasid(), shall we enforce that the
>> set_dev_pasid() op of blocked_domain to be always success. Is it?
> 
> Yes. The semantics of blocking domain is that the iommu driver must
> ensure successful completion.

great. thanks for the confirmation.

-- 
Regards,
Yi Liu

  reply	other threads:[~2024-09-06  5:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28  9:05 [PATCH v3 0/7] iommufd support pasid attach/replace Yi Liu
2024-06-28  9:05 ` [PATCH v3 1/7] iommu: Introduce a replace API for device pasid Yi Liu
2024-07-18  8:27   ` Tian, Kevin
2024-08-16  9:43     ` Yi Liu
2024-08-16 13:02       ` Jason Gunthorpe
2024-09-06  4:21         ` Yi Liu
2024-09-06  4:33           ` Baolu Lu
2024-09-06  5:57             ` Yi Liu [this message]
2024-06-28  9:05 ` [PATCH v3 2/7] iommufd: Pass pasid through the device attach/replace path Yi Liu
2024-06-28  9:05 ` [PATCH v3 3/7] iommufd: Support attach/replace hwpt per pasid Yi Liu
2024-06-28  9:05 ` [PATCH v3 4/7] iommufd/selftest: Add set_dev_pasid and remove_dev_pasid in mock iommu Yi Liu
2024-06-28  9:05 ` [PATCH v3 5/7] iommufd/selftest: Add a helper to get test device Yi Liu
2024-06-28  9:05 ` [PATCH v3 6/7] iommufd/selftest: Add test ops to test pasid attach/detach Yi Liu
2024-06-28  9:05 ` [PATCH v3 7/7] iommufd/selftest: Add coverage for iommufd " Yi Liu

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=6871e983-ae3a-42c8-ac63-570ba422df7e@intel.com \
    --to=yi.l.liu@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=eric.auger@redhat.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=vasant.hegde@amd.com \
    --cc=zhenzhong.duan@intel.com \
    /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