[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKHBV27xxvzK55C7nT8HgcF2G6SpF7ssxYK7D0+t_dS6PODE5A@mail.gmail.com>
Date: Fri, 18 Aug 2023 11:14:11 +0800
From: Michael Shavit <mshavit@...gle.com>
To: Robin Murphy <robin.murphy@....com>
Cc: iommu@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, will@...nel.org, jgg@...dia.com,
nicolinc@...dia.com, tina.zhang@...el.com, jean-philippe@...aro.org
Subject: Re: [RFC PATCH v1 4/8] iommu/arm-smmu-v3: check smmu compatibility on attach
On Fri, Aug 18, 2023 at 3:17 AM Robin Murphy <robin.murphy@....com> wrote:
>
> On 2023-08-17 19:16, Michael Shavit wrote:
> > Record the domain's pgtbl_cfg when it's being prepared so that it can
> > later be compared to the features an smmu supports.
>
> What's wrong with retrieving the existing config from the
> io_pgtable_ops, same as all the other io-pgtable code does?
>
I didn't think accessing the io_pgtable struct outside of io-pgtable
code would be ok, but now that you mention it I do see usages of
io_pgtable_ops_to_pgtable in iommu drivers.
Will change.
Powered by blists - more mailing lists