From: Boris Brezillon <boris.brezillon@collabora.com>
To: Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
Steven Price <steven.price@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org
Subject: [PATCH v2 0/5] drm/panfrost: Add extra GPU-usage flags
Date: Fri, 1 Oct 2021 16:34:22 +0200 [thread overview]
Message-ID: <20211001143427.1564786-1-boris.brezillon@collabora.com> (raw)
Hello,
This is a follow-up of [1], which was adding the read/write
restrictions on GPU buffers. Robin and Steven suggested that I add a
flag to restrict the shareability domain on GPU-private buffers, so
here it is.
As you can see, the first patch is flagges RFC, since I'm not sure
adding a new IOMMU_ flag is the right solution, but IOMMU_CACHE
doesn't feel like a good fit either. Please let me know if you have
better ideas.
Regards,
Boris
[1]https://patchwork.kernel.org/project/dri-devel/patch/20210930184723.1482426-1-boris.brezillon@collabora.com/
Boris Brezillon (5):
[RFC]iommu: Add a IOMMU_DEVONLY protection flag
[RFC]iommu/io-pgtable-arm: Take the DEVONLY flag into account on
ARM_MALI_LPAE
drm/panfrost: Add PANFROST_BO_NO{READ,WRITE} flags
drm/panfrost: Add a PANFROST_BO_GPUONLY flag
drm/panfrost: Bump the driver version to 1.3
drivers/gpu/drm/panfrost/panfrost_drv.c | 15 +++++++++++++--
drivers/gpu/drm/panfrost/panfrost_gem.c | 3 +++
drivers/gpu/drm/panfrost/panfrost_gem.h | 3 +++
drivers/gpu/drm/panfrost/panfrost_mmu.c | 11 ++++++++++-
drivers/iommu/io-pgtable-arm.c | 25 +++++++++++++++++--------
include/linux/iommu.h | 7 +++++++
include/uapi/drm/panfrost_drm.h | 3 +++
7 files changed, 56 insertions(+), 11 deletions(-)
--
2.31.1
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
Steven Price <steven.price@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Cc: dri-devel@lists.freedesktop.org,
Boris Brezillon <boris.brezillon@collabora.com>
Subject: [PATCH v2 0/5] drm/panfrost: Add extra GPU-usage flags
Date: Fri, 1 Oct 2021 16:34:22 +0200 [thread overview]
Message-ID: <20211001143427.1564786-1-boris.brezillon@collabora.com> (raw)
Hello,
This is a follow-up of [1], which was adding the read/write
restrictions on GPU buffers. Robin and Steven suggested that I add a
flag to restrict the shareability domain on GPU-private buffers, so
here it is.
As you can see, the first patch is flagges RFC, since I'm not sure
adding a new IOMMU_ flag is the right solution, but IOMMU_CACHE
doesn't feel like a good fit either. Please let me know if you have
better ideas.
Regards,
Boris
[1]https://patchwork.kernel.org/project/dri-devel/patch/20210930184723.1482426-1-boris.brezillon@collabora.com/
Boris Brezillon (5):
[RFC]iommu: Add a IOMMU_DEVONLY protection flag
[RFC]iommu/io-pgtable-arm: Take the DEVONLY flag into account on
ARM_MALI_LPAE
drm/panfrost: Add PANFROST_BO_NO{READ,WRITE} flags
drm/panfrost: Add a PANFROST_BO_GPUONLY flag
drm/panfrost: Bump the driver version to 1.3
drivers/gpu/drm/panfrost/panfrost_drv.c | 15 +++++++++++++--
drivers/gpu/drm/panfrost/panfrost_gem.c | 3 +++
drivers/gpu/drm/panfrost/panfrost_gem.h | 3 +++
drivers/gpu/drm/panfrost/panfrost_mmu.c | 11 ++++++++++-
drivers/iommu/io-pgtable-arm.c | 25 +++++++++++++++++--------
include/linux/iommu.h | 7 +++++++
include/uapi/drm/panfrost_drm.h | 3 +++
7 files changed, 56 insertions(+), 11 deletions(-)
--
2.31.1
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
Steven Price <steven.price@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Cc: dri-devel@lists.freedesktop.org,
Boris Brezillon <boris.brezillon@collabora.com>
Subject: [PATCH v2 0/5] drm/panfrost: Add extra GPU-usage flags
Date: Fri, 1 Oct 2021 16:34:22 +0200 [thread overview]
Message-ID: <20211001143427.1564786-1-boris.brezillon@collabora.com> (raw)
Hello,
This is a follow-up of [1], which was adding the read/write
restrictions on GPU buffers. Robin and Steven suggested that I add a
flag to restrict the shareability domain on GPU-private buffers, so
here it is.
As you can see, the first patch is flagges RFC, since I'm not sure
adding a new IOMMU_ flag is the right solution, but IOMMU_CACHE
doesn't feel like a good fit either. Please let me know if you have
better ideas.
Regards,
Boris
[1]https://patchwork.kernel.org/project/dri-devel/patch/20210930184723.1482426-1-boris.brezillon@collabora.com/
Boris Brezillon (5):
[RFC]iommu: Add a IOMMU_DEVONLY protection flag
[RFC]iommu/io-pgtable-arm: Take the DEVONLY flag into account on
ARM_MALI_LPAE
drm/panfrost: Add PANFROST_BO_NO{READ,WRITE} flags
drm/panfrost: Add a PANFROST_BO_GPUONLY flag
drm/panfrost: Bump the driver version to 1.3
drivers/gpu/drm/panfrost/panfrost_drv.c | 15 +++++++++++++--
drivers/gpu/drm/panfrost/panfrost_gem.c | 3 +++
drivers/gpu/drm/panfrost/panfrost_gem.h | 3 +++
drivers/gpu/drm/panfrost/panfrost_mmu.c | 11 ++++++++++-
drivers/iommu/io-pgtable-arm.c | 25 +++++++++++++++++--------
include/linux/iommu.h | 7 +++++++
include/uapi/drm/panfrost_drm.h | 3 +++
7 files changed, 56 insertions(+), 11 deletions(-)
--
2.31.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-10-01 14:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 14:34 Boris Brezillon [this message]
2021-10-01 14:34 ` [PATCH v2 0/5] drm/panfrost: Add extra GPU-usage flags Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
2021-10-01 14:34 ` [PATCH v2 1/5] [RFC]iommu: Add a IOMMU_DEVONLY protection flag Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
2021-10-01 17:31 ` Alyssa Rosenzweig
2021-10-01 17:31 ` Alyssa Rosenzweig
2021-10-01 17:31 ` Alyssa Rosenzweig
2021-10-18 10:25 ` Joerg Roedel
2021-10-18 10:25 ` Joerg Roedel
2021-10-18 10:25 ` Joerg Roedel
2021-10-18 12:03 ` Boris Brezillon
2021-10-18 12:03 ` Boris Brezillon
2021-10-18 12:03 ` Boris Brezillon
2021-10-01 14:34 ` [PATCH v2 2/5] [RFC]iommu/io-pgtable-arm: Take the DEVONLY flag into account on ARM_MALI_LPAE Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
2021-10-01 14:34 ` [PATCH v2 3/5] drm/panfrost: Add PANFROST_BO_NO{READ,WRITE} flags Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
2021-10-01 14:36 ` Boris Brezillon
2021-10-01 14:36 ` Boris Brezillon
2021-10-01 14:36 ` Boris Brezillon
2021-10-01 14:34 ` [PATCH v2 4/5] drm/panfrost: Add a PANFROST_BO_GPUONLY flag Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
2021-10-01 15:13 ` Steven Price
2021-10-01 15:13 ` Steven Price
2021-10-01 15:13 ` Steven Price
2021-10-01 16:22 ` Boris Brezillon
2021-10-01 16:22 ` Boris Brezillon
2021-10-01 16:22 ` Boris Brezillon
2021-10-01 17:30 ` Alyssa Rosenzweig
2021-10-01 17:30 ` Alyssa Rosenzweig
2021-10-01 17:30 ` Alyssa Rosenzweig
2021-10-01 14:34 ` [PATCH v2 5/5] drm/panfrost: Bump the driver version to 1.3 Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
2021-10-01 14:34 ` Boris Brezillon
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=20211001143427.1564786-1-boris.brezillon@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.