From: Jason Gunthorpe <jgg@nvidia.com>
To: Michael Shavit <mshavit@google.com>
Cc: iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, will@kernel.org,
robin.murphy@arm.com, nicolinc@nvidia.com,
jean-philippe@linaro.org, tina.zhang@intel.com,
Joerg Roedel <joro@8bytes.org>, Kevin Tian <kevin.tian@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Mark Brown <broonie@kernel.org>, Tomas Krcka <krckatom@amazon.de>,
Yicong Yang <yangyicong@hisilicon.com>
Subject: Re: [PATCH v1 3/3] iommu/arm-smmu-v3-sva: Remove arm_smmu_bond
Date: Tue, 5 Sep 2023 15:16:49 -0300 [thread overview]
Message-ID: <ZPdwkX3Yne0ahWIL@nvidia.com> (raw)
In-Reply-To: <CAKHBV27=sTW3jXqqCJCPfMFRq=h8_S4JSrSAx61pfWqKrCak0w@mail.gmail.com>
On Tue, Sep 05, 2023 at 09:14:09PM +0800, Michael Shavit wrote:
> On Tue, Sep 5, 2023 at 8:42 PM Jason Gunthorpe <jgg@nvidia.com> wrote:
> >
> > On Tue, Sep 05, 2023 at 07:49:14PM +0800, Michael Shavit wrote:
> > > Create a new iommu_domain subclass for SVA iommu domains to hold the
> > > data previously stored in the dynamically allocated arm_smmu_bond. Add a
> > > simple count of attached SVA domains to arm_smmu_master to replace the
> > > list of bonds.
> > >
> > > Signed-off-by: Michael Shavit <mshavit@google.com>
> > > ---
> > >
> > > .../iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c | 70 +++++++------------
> > > drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 1 -
> > > drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 2 +-
> > > 3 files changed, 26 insertions(+), 47 deletions(-)
> > >
> > > diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c
> > > index 9fb6907c5e7d4..0342c0f35d55a 100644
> > > --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c
> > > +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c
> > > @@ -24,14 +24,13 @@ struct arm_smmu_mmu_notifier {
> > >
> > > #define mn_to_smmu(mn) container_of(mn, struct arm_smmu_mmu_notifier, mn)
> > >
> > > -struct arm_smmu_bond {
> > > - struct mm_struct *mm;
> > > +struct arm_smmu_sva_domain {
> > > + struct iommu_domain iommu_domain;
> > > struct arm_smmu_mmu_notifier *smmu_mn;
> > > - struct list_head list;
> > > };
> > >
> > > -#define sva_to_bond(handle) \
> > > - container_of(handle, struct arm_smmu_bond, sva)
> > > +#define to_sva_domain(domain) \
> > > + container_of(domain, struct arm_smmu_sva_domain, iommu_domain)
> >
> > I'm not sure about this? This seems like a strange direction
> >
> > The SVA domain and a UNMANAGED/PAGING domain should be basically the
> > same thing. Making a sva_domain a completely different type looks like
> > it would stand in the way of that?
>
> Agreed that's the eventual destination of all these re-works, but the
> stage isn't fully set for that yet. IMO this is a simpler improvement
> to get through for now, and I don't see it being an obstacle in the
> future.
Well, OK, you have the followup patches..
But I don't want to get in a spot where we continue to have "primary
domains" for SVA..
Jason
next prev parent reply other threads:[~2023-09-05 18:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 11:49 [PATCH v1 0/3] Clean-up arm-smmu-v3-sva.c: remove arm_smmu_bond Michael Shavit
2023-09-05 11:49 ` [PATCH v1 1/3] iommu/arm-smmu-v3-sva: Remove unused iommu_sva handle Michael Shavit
2023-09-05 12:36 ` Jason Gunthorpe
2023-09-05 11:49 ` [PATCH v1 2/3] iommu/arm-smmu-v3-sva: Remove bond refcount Michael Shavit
2023-09-05 12:38 ` Jason Gunthorpe
2023-09-05 11:49 ` [PATCH v1 3/3] iommu/arm-smmu-v3-sva: Remove arm_smmu_bond Michael Shavit
2023-09-05 12:42 ` Jason Gunthorpe
2023-09-05 13:14 ` Michael Shavit
2023-09-05 18:16 ` Jason Gunthorpe [this message]
2023-09-05 12:35 ` [PATCH v1 0/3] Clean-up arm-smmu-v3-sva.c: remove arm_smmu_bond Jason Gunthorpe
2023-09-05 13:24 ` Michael Shavit
2023-09-05 13:32 ` Jason Gunthorpe
2023-10-12 18:06 ` Will Deacon
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=ZPdwkX3Yne0ahWIL@nvidia.com \
--to=jgg@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=broonie@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=krckatom@amazon.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mshavit@google.com \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=tina.zhang@intel.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.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