[PATCH v2 1/5] [RFC]iommu: Add a IOMMU_DEVONLY protection flag
Boris Brezillon
boris.brezillon at collabora.com
Mon Oct 18 12:03:56 UTC 2021
Hello Joerg,
On Mon, 18 Oct 2021 12:25:38 +0200
Joerg Roedel <joro at 8bytes.org> wrote:
> On Fri, Oct 01, 2021 at 04:34:23PM +0200, Boris Brezillon wrote:
> > +/*
> > + * Mapping is only accessed by the device behind the iommu. That means other
> > + * devices or CPUs are not expected to access this physical memory region,
> > + * and the MMU driver can safely restrict the shareability domain to the
> > + * device itself.
> > + */
> > +#define IOMMU_DEVONLY (1 << 6)
>
> I am not entirely happy with the name, how about
>
> IOMMU_DEV_PRIVATE?
Works for me.
>
> PRIV would conflict with IOMMU_PRIV (which should probably also be
> IOMMU_PRIVILEGED, but thats another problem).
Yeah, IOMMU_PRIV is confusing. I thought I could use that flag before
realizing PRIV was for privileged not private, but I'll leave that to
someone else :-).
Regards,
Boris
More information about the dri-devel
mailing list