From: Keqian Zhu <zhukeqian1@huawei.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
jiangkunkun@huawei.com, kvm@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
Will Deacon <will@kernel.org>,
kvmarm@lists.cs.columbia.edu, Marc Zyngier <maz@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
wanghaibin.wang@huawei.com,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Alexios Zavras <alexios.zavras@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
Cornelia Huck <cohuck@redhat.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
James Morse <james.morse@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH 4/5] vfio/iommu_type1: Carefully use unmap_unpin_all during dirty tracking
Date: Thu, 14 Jan 2021 20:11:00 +0800 [thread overview]
Message-ID: <14ee2346-ea9e-ab24-40d7-45a3bd16510d@huawei.com> (raw)
In-Reply-To: <20210112125331.789f47a5@omen.home.shazbot.org>
On 2021/1/13 3:53, Alex Williamson wrote:
> On Tue, 12 Jan 2021 20:04:38 +0800
> Keqian Zhu <zhukeqian1@huawei.com> wrote:
>
>> On 2021/1/12 5:49, Alex Williamson wrote:
>>> On Thu, 7 Jan 2021 17:29:00 +0800
>>> Keqian Zhu <zhukeqian1@huawei.com> wrote:
>>>
>>>> If we detach group during dirty page tracking, we shouldn't remove
>>>> vfio_dma, because dirty log will lose.
>>>>
>>>> But we don't prevent unmap_unpin_all in vfio_iommu_release, because
>>>> under normal procedure, dirty tracking has been stopped.
>>>
>>> This looks like it's creating a larger problem than it's fixing, it's
>>> not our job to maintain the dirty bitmap regardless of what the user
>>> does. If the user detaches the last group in a container causing the
>>> mappings within that container to be deconstructed before the user has
>>> collected dirty pages, that sounds like a user error. A container with
>>> no groups is de-privileged and therefore loses all state. Thanks,
>>>
>>> Alex
>>
>> Hi Alex,
>>
>> This looks good to me ;-). That's a reasonable constraint for user behavior.
>>
>> What about replacing this patch with an addition to the uapi document of
>> VFIO_GROUP_UNSET_CONTAINER? User should pay attention to this when call this
>> ioctl during dirty tracking.
>
> Here's the current uapi comment:
>
> /**
> * VFIO_GROUP_UNSET_CONTAINER - _IO(VFIO_TYPE, VFIO_BASE + 5)
> *
> * Remove the group from the attached container. This is the
> * opposite of the SET_CONTAINER call and returns the group to
> * an initial state. All device file descriptors must be released
> * prior to calling this interface. When removing the last group
> * from a container, the IOMMU will be disabled and all state lost,
> * effectively also returning the VFIO file descriptor to an initial
> * state.
> * Return: 0 on success, -errno on failure.
> * Availability: When attached to container
> */
>
> So we already indicate that "all state" of the container is lost when
> removing the last group, I don't see that it's necessarily to
> explicitly include dirty bitmap state beyond that statement. Without
> mappings there can be no dirty bitmap to track.
OK :-) .
>
> > And any comments on other patches? thanks.
>
> I had a difficult time mapping the commit log to the actual code
> change, I'll likely have some wording suggestions. Is patch 5/5 still
> necessary if this patch is dropped? Thanks,
>
I think the 5th patch is still necessary. vfio_sanity_check_pfn_list() is used to check
whether pfn_list of vfio_dma is empty. but we apply this check just for external domain.
If the iommu backed domain also pin some pages, then this check fails. So I think we should
use this check only when all domains are about to be removed.
Besides, this patch should extract the "WARN_ON(iommu->notifier.head);" just for external domain.
Thanks,
Keqian
> Alex
>
>>>> Fixes: d6a4c185660c ("vfio iommu: Implementation of ioctl for dirty pages tracking")
>>>> Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com>
>>>> ---
>>>> drivers/vfio/vfio_iommu_type1.c | 14 ++++++++++++--
>>>> 1 file changed, 12 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
>>>> index 26b7eb2a5cfc..9776a059904d 100644
>>>> --- a/drivers/vfio/vfio_iommu_type1.c
>>>> +++ b/drivers/vfio/vfio_iommu_type1.c
>>>> @@ -2373,7 +2373,12 @@ static void vfio_iommu_type1_detach_group(void *iommu_data,
>>>> if (list_empty(&iommu->external_domain->group_list)) {
>>>> vfio_sanity_check_pfn_list(iommu);
>>>>
>>>> - if (!IS_IOMMU_CAP_DOMAIN_IN_CONTAINER(iommu))
>>>> + /*
>>>> + * During dirty page tracking, we can't remove
>>>> + * vfio_dma because dirty log will lose.
>>>> + */
>>>> + if (!IS_IOMMU_CAP_DOMAIN_IN_CONTAINER(iommu) &&
>>>> + !iommu->dirty_page_tracking)
>>>> vfio_iommu_unmap_unpin_all(iommu);
>>>>
>>>> kfree(iommu->external_domain);
>>>> @@ -2406,10 +2411,15 @@ static void vfio_iommu_type1_detach_group(void *iommu_data,
>>>> * iommu and external domain doesn't exist, then all the
>>>> * mappings go away too. If it's the last domain with iommu and
>>>> * external domain exist, update accounting
>>>> + *
>>>> + * Note: During dirty page tracking, we can't remove vfio_dma
>>>> + * because dirty log will lose. Just update accounting is a good
>>>> + * choice.
>>>> */
>>>> if (list_empty(&domain->group_list)) {
>>>> if (list_is_singular(&iommu->domain_list)) {
>>>> - if (!iommu->external_domain)
>>>> + if (!iommu->external_domain &&
>>>> + !iommu->dirty_page_tracking)
>>>> vfio_iommu_unmap_unpin_all(iommu);
>>>> else
>>>> vfio_iommu_unmap_unpin_reaccount(iommu);
>>>
>>> .
>>>
>>
>
> .
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-01-14 12:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 9:28 [PATCH 0/5] vfio/iommu_type1: Some fixes about dirty tracking Keqian Zhu
2021-01-07 9:28 ` [PATCH 1/5] vfio/iommu_type1: Fixes vfio_dma_populate_bitmap to avoid dirty lose Keqian Zhu
2021-01-12 21:20 ` Alex Williamson
2021-01-13 12:35 ` Kirti Wankhede
2021-01-13 15:13 ` Alex Williamson
2021-01-14 13:05 ` Keqian Zhu
2021-01-14 17:14 ` Alex Williamson
2021-01-15 9:41 ` Keqian Zhu
2021-01-07 9:28 ` [PATCH 2/5] vfio/iommu_type1: Populate dirty bitmap for new vfio_dma Keqian Zhu
2021-01-07 9:28 ` [PATCH 3/5] vfio/iommu_type1: Populate dirty bitmap when attach group Keqian Zhu
2021-01-07 9:29 ` [PATCH 4/5] vfio/iommu_type1: Carefully use unmap_unpin_all during dirty tracking Keqian Zhu
2021-01-11 21:49 ` Alex Williamson
2021-01-12 12:04 ` Keqian Zhu
2021-01-12 19:53 ` Alex Williamson
2021-01-14 12:11 ` Keqian Zhu [this message]
2021-01-07 9:29 ` [PATCH 5/5] vfio/iommu_type1: Move sanity_check_pfn_list to unmap_unpin_all Keqian Zhu
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=14ee2346-ea9e-ab24-40d7-45a3bd16510d@huawei.com \
--to=zhukeqian1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=alexios.zavras@intel.com \
--cc=catalin.marinas@arm.com \
--cc=cohuck@redhat.com \
--cc=daniel.lezcano@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=james.morse@arm.com \
--cc=jiangkunkun@huawei.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kwankhede@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=robin.murphy@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
--cc=wanghaibin.wang@huawei.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