From: Jason Gunthorpe <jgg@nvidia.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Cc: Joao Martins <joao.m.martins@oracle.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"mshavit@google.com" <mshavit@google.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"will@kernel.org" <will@kernel.org>,
jiangkunkun <jiangkunkun@huawei.com>,
zhukeqian <zhukeqian1@huawei.com>, Linuxarm <linuxarm@huawei.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 3/4] iommu/arm-smmu-v3: Add support for dirty tracking in domain alloc
Date: Thu, 22 Feb 2024 09:11:01 -0400 [thread overview]
Message-ID: <20240222131101.GZ13330@nvidia.com> (raw)
In-Reply-To: <d6442be07c9d4f999286e073ed221984@huawei.com>
On Thu, Feb 22, 2024 at 12:24:06PM +0000, Shameerali Kolothum Thodi wrote:
> > > Ok. But do we really need to check this in attach()? As dirty_ops are added only
> > > if it is requested in alloc_user() and there we return err when hardware doesn't
> > > have the capability. So not sure how this matters in attach() path. May be I am
> > > missing something.
> >
> > That's when you create the domain with dev A. Afterwards that dev A is
> > attached,
> > but later on you can attach another device B to the domain. So this check is
> > there such that a domain with dirty tracking ops set will only have devices in
> > there that support dirty tracking.
>
> But that only matters if dev B is on different smmu without dbm capability, right?
> In that case we already fail the attach with,
>
> >>> } else if (smmu_domain->smmu != smmu)
> > >>> ret = -EINVAL;
> > >>>
>
> Is that right?
Right. Relaxing this is on my list :\
The other two drivers don't have this limitation so needed the check
that Joao described.
Jason
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-22 13:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 9:49 [PATCH v2 0/4] iommu/smmuv3: Add IOMMUFD dirty tracking support for SMMUv3 Shameer Kolothum
2024-02-22 9:49 ` [PATCH v2 1/4] iommu/arm-smmu-v3: Add feature detection for HTTU Shameer Kolothum
2024-04-23 14:41 ` Ryan Roberts
2024-04-23 14:52 ` Jason Gunthorpe
2024-04-24 10:04 ` Ryan Roberts
2024-04-24 12:23 ` Jason Gunthorpe
2024-04-24 12:59 ` Ryan Roberts
2024-04-24 13:20 ` Shameerali Kolothum Thodi
2024-04-24 13:32 ` Jason Gunthorpe
2024-04-24 13:43 ` Shameerali Kolothum Thodi
2024-04-24 14:21 ` Jason Gunthorpe
2024-04-24 8:01 ` Shameerali Kolothum Thodi
2024-04-24 8:28 ` Ryan Roberts
2024-02-22 9:49 ` [PATCH v2 2/4] iommu/io-pgtable-arm: Add read_and_clear_dirty() support Shameer Kolothum
2024-04-23 15:56 ` Ryan Roberts
2024-04-24 8:01 ` Shameerali Kolothum Thodi
2024-04-24 8:36 ` Ryan Roberts
2024-02-22 9:49 ` [PATCH v2 3/4] iommu/arm-smmu-v3: Add support for dirty tracking in domain alloc Shameer Kolothum
2024-02-22 11:04 ` Joao Martins
2024-02-22 11:31 ` Shameerali Kolothum Thodi
2024-02-22 11:37 ` Joao Martins
2024-02-22 12:24 ` Shameerali Kolothum Thodi
2024-02-22 13:11 ` Jason Gunthorpe [this message]
2024-02-22 13:23 ` Joao Martins
2024-03-08 14:31 ` Jason Gunthorpe
2024-04-23 16:27 ` Ryan Roberts
2024-04-23 16:39 ` Jason Gunthorpe
2024-04-23 16:50 ` Ryan Roberts
2024-04-24 8:27 ` Shameerali Kolothum Thodi
2024-02-22 9:49 ` [PATCH v2 4/4] iommu/arm-smmu-v3: Enable HTTU for stage1 with io-pgtable mapping Shameer Kolothum
2024-03-08 14:32 ` Jason Gunthorpe
2024-04-23 16:45 ` Ryan Roberts
2024-04-23 17:32 ` Jason Gunthorpe
2024-04-24 7:58 ` Ryan Roberts
2024-04-24 12:15 ` Jason Gunthorpe
2024-04-24 12:45 ` Ryan Roberts
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=20240222131101.GZ13330@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jiangkunkun@huawei.com \
--cc=joao.m.martins@oracle.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=mshavit@google.com \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=will@kernel.org \
--cc=zhukeqian1@huawei.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;
as well as URLs for NNTP newsgroup(s).