drm/msm: support for host-cached BOs
Subsystems (5)
cover drm/msm: support for host-cached BOs
This is to support cached and cached-coherent memory types in vulkan.
I made a corresponding WIP merge request [1] which shows usage of this.
[1] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6949
Jonathan Marek (3):
drm/msm: add MSM_BO_CACHED_COHERENT
drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance drm/msm: bump up the uapi version
drivers/gpu/drm/msm/adreno/adreno_device.c | 1 + drivers/gpu/drm/msm/msm_drv.c | 24 ++++++++++++++++++++- drivers/gpu/drm/msm/msm_drv.h | 3 +++ drivers/gpu/drm/msm/msm_gem.c | 23 ++++++++++++++++++++ include/uapi/drm/msm_drm.h | 25 +++++++++++++++++++--- 5 files changed, 72 insertions(+), 4 deletions(-)
Signature · 1 line
2.26.1
PATCH 1/3 drm/msm: add MSM_BO_CACHED_COHERENT
Add a new cache mode for creating coherent host-cached BOs.
--- drivers/gpu/drm/msm/adreno/adreno_device.c | 1 + drivers/gpu/drm/msm/msm_drv.h | 1 + drivers/gpu/drm/msm/msm_gem.c | 8 ++++++++ include/uapi/drm/msm_drm.h | 5 ++--- 4 files changed, 12 insertions(+), 3 deletions(-)
drivers/gpu/drm/msm/adreno/adreno_device.c +1 -0
@@ -410,6 +410,7 @@ static int adreno_bind(struct device *dev, struct device *master, void *data) config.rev.minor, config.rev.patchid); priv->is_a2xx = config.rev.core ==2 ; + priv->has_cached_coherent = config.rev.core >=6 ; gpu = info->init (drm);if (IS_ERR (gpu)) {
drivers/gpu/drm/msm/msm_drv.h +1 -0
@@ -167,6 +167,7 @@ struct msm_drm_private {struct msm_file_private *lastctx;/* gpu is only set on open(), but we need this info earlier */ bool is_a2xx; +bool has_cached_coherent;struct drm_fb_helper *fbdev;
drivers/gpu/drm/msm/msm_gem.c +8 -0
@@ -431,6 +431,9 @@ static int msm_gem_pin_iova(struct drm_gem_object *obj,if (msm_obj->flags &MSM_BO_MAP_PRIV ) prot |=IOMMU_PRIV ; +if (msm_obj->flags &MSM_BO_CACHED_COHERENT ) + prot |=IOMMU_CACHE ; +WARN_ON (!mutex_is_locked (&msm_obj->lock));if (WARN_ON (msm_obj->madv !=MSM_MADV_WILLNEED ))
@@ -998,6 +1001,7 @@ static int msm_gem_new_impl(struct drm_device *dev, uint32_t size, uint32_t flags, struct drm_gem_object **obj) { + struct msm_drm_private *priv = dev->dev_private;struct msm_gem_object *msm_obj;switch (flags &MSM_BO_CACHE_MASK ) {
@@ -1005,6 +1009,10 @@ static int msm_gem_new_impl(struct drm_device *dev,case MSM_BO_CACHED :case MSM_BO_WC :break ; +case MSM_BO_CACHED_COHERENT : +if (priv->has_cached_coherent) +break ; +/* fallthrough */ default :DRM_DEV_ERROR (dev->dev,"invalid cache flag: %x\n" , (flags &MSM_BO_CACHE_MASK ));
include/uapi/drm/msm_drm.h +2 -3
@@ -94,12 +94,11 @@ struct drm_msm_param {#define MSM_BO_CACHED 0x00010000#define MSM_BO_WC 0x00020000#define MSM_BO_UNCACHED 0x00040000 +#define MSM_BO_CACHED_COHERENT 0x080000#define MSM_BO_FLAGS (MSM_BO_SCANOUT | \ MSM_BO_GPU_READONLY | \ - MSM_BO_CACHED | \ - MSM_BO_WC | \ - MSM_BO_UNCACHED) + MSM_BO_CACHE_MASK)struct drm_msm_gem_new {__u64 size;/* in */
Signature · 1 line
2.26.1
Re: [PATCH 1/3] drm/msm: add MSM_BO_CACHED_COHERENT
Quoted 1 line · Jonathan Marek
Add a new cache mode for creating coherent host-cached BOs.
Quoted 55 lines
Signed-off-by Jonathan Marek <[email protected]>--- drivers/gpu/drm/msm/adreno/adreno_device.c | 1 + drivers/gpu/drm/msm/msm_drv.h | 1 + drivers/gpu/drm/msm/msm_gem.c | 8 ++++++++ include/uapi/drm/msm_drm.h | 5 ++--- 4 files changed, 12 insertions(+), 3 deletions(-)drivers/gpu/drm/msm/adreno/adreno_device.c +1
-0@@ -410,6 +410,7 @@ static int adreno_bind(struct device *dev, struct device *master, void *data) config.rev.minor, config.rev.patchid); priv->is_a2xx = config.rev.core ==2 ; + priv->has_cached_coherent = config.rev.core >=6 ; gpu = info->init (drm);if (IS_ERR (gpu)) {drivers/gpu/drm/msm/msm_drv.h +1
-0@@ -167,6 +167,7 @@ struct msm_drm_private {struct msm_file_private *lastctx;/* gpu is only set on open(), but we need this info earlier */ bool is_a2xx; +bool has_cached_coherent;struct drm_fb_helper *fbdev;drivers/gpu/drm/msm/msm_gem.c +4
-0@@ -431,6 +431,9 @@ static int msm_gem_pin_iova(struct drm_gem_object *obj,if (msm_obj->flags &MSM_BO_MAP_PRIV ) prot |=IOMMU_PRIV ; +if (msm_obj->flags &MSM_BO_CACHED_COHERENT ) + prot |=IOMMU_CACHE ; +WARN_ON (!mutex_is_locked (&msm_obj->lock));if (WARN_ON (msm_obj->madv !=MSM_MADV_WILLNEED ))@@ -998,6 +1001,7 @@ static int msm_gem_new_impl(struct drm_device *dev, uint32_t size, uint32_t flags, struct drm_gem_object **obj) { + struct msm_drm_private *priv = dev->dev_private;struct msm_gem_object *msm_obj;switch (flags &MSM_BO_CACHE_MASK ) {
drivers/gpu/drm/msm/msm_gem.c static int msm_gem_new_impl(struct drm_device *dev, · line 1015
Quoted 7 lines
drivers/gpu/drm/msm/msm_gem.c +4
-0@@ -1005,6 +1009,10 @@ static int msm_gem_new_impl(struct drm_device *dev,case MSM_BO_CACHED :case MSM_BO_WC :break ; +case MSM_BO_CACHED_COHERENT : +if (priv->has_cached_coherent) +break ; +/* fallthrough */
It confused me that this kind of implicitly fell into the else clause in msm_gem_mmap_obj, but I'm on board. This is a good solution since it only allows I/O coherence with caching.
Quoted 25 lines
drivers/gpu/drm/msm/msm_gem.c +0
-0default :DRM_DEV_ERROR (dev->dev,"invalid cache flag: %x\n" , (flags &MSM_BO_CACHE_MASK ));include/uapi/drm/msm_drm.h +2
-3@@ -94,12 +94,11 @@ struct drm_msm_param {#define MSM_BO_CACHED 0x00010000#define MSM_BO_WC 0x00020000#define MSM_BO_UNCACHED 0x00040000 +#define MSM_BO_CACHED_COHERENT 0x080000#define MSM_BO_FLAGS (MSM_BO_SCANOUT | \ MSM_BO_GPU_READONLY | \ - MSM_BO_CACHED | \ - MSM_BO_WC | \ - MSM_BO_UNCACHED) + MSM_BO_CACHE_MASK)struct drm_msm_gem_new {__u64 size;/* in */ Signature · 1 line
2.26.1
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
PATCH 2/3 drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
In reply to Jonathan MarekThis makes it possible to use the non-coherent cached MSM_BO_CACHED mode, which otherwise doesn't provide any method for cleaning/invalidating the cache to sync with the device.
--- drivers/gpu/drm/msm/msm_drv.c | 21 +++++++++++++++++++++ drivers/gpu/drm/msm/msm_drv.h | 2 ++ drivers/gpu/drm/msm/msm_gem.c | 15 +++++++++++++++ include/uapi/drm/msm_drm.h | 20 ++++++++++++++++++++ 4 files changed, 58 insertions(+)
drivers/gpu/drm/msm/msm_drv.c +21 -0
@@ -964,6 +964,26 @@ static int msm_ioctl_submitqueue_close(struct drm_device *dev, void *data,return msm_submitqueue_remove (file->driver_priv, id); } +static int msm_ioctl_gem_sync_cache (struct drm_device *dev,void *data, +struct drm_file *file) +{ +struct drm_msm_gem_sync_cache *args = data; +struct drm_gem_object *obj; + +if (args->flags & ~MSM_GEM_SYNC_CACHE_FLAGS ) +return -EINVAL ; + + obj =drm_gem_object_lookup (file, args->handle); +if (!obj) +return -ENOENT ; + +msm_gem_sync_cache (obj, args->flags, args->offset, args->end); + +drm_gem_object_put (obj); + +return 0 ; +} +static const struct drm_ioctl_desc msm_ioctls[] = {DRM_IOCTL_DEF_DRV (MSM_GET_PARAM , msm_ioctl_get_param,DRM_RENDER_ALLOW ),DRM_IOCTL_DEF_DRV (MSM_GEM_NEW , msm_ioctl_gem_new,DRM_RENDER_ALLOW ),
@@ -976,6 +996,7 @@ static const struct drm_ioctl_desc msm_ioctls[] = {DRM_IOCTL_DEF_DRV (MSM_SUBMITQUEUE_NEW , msm_ioctl_submitqueue_new,DRM_RENDER_ALLOW ),DRM_IOCTL_DEF_DRV (MSM_SUBMITQUEUE_CLOSE , msm_ioctl_submitqueue_close,DRM_RENDER_ALLOW ),DRM_IOCTL_DEF_DRV (MSM_SUBMITQUEUE_QUERY , msm_ioctl_submitqueue_query,DRM_RENDER_ALLOW ), + DRM_IOCTL_DEF_DRV(MSM_GEM_SYNC_CACHE, msm_ioctl_gem_sync_cache, DRM_RENDER_ALLOW), }; static const struct vm_operations_struct vm_ops = {
drivers/gpu/drm/msm/msm_drv.h +2 -0
@@ -314,6 +314,8 @@ void msm_gem_move_to_active(struct drm_gem_object *obj,void msm_gem_move_to_inactive (struct drm_gem_object *obj);int msm_gem_cpu_prep (struct drm_gem_object *obj,uint32_t op,ktime_t *timeout);int msm_gem_cpu_fini (struct drm_gem_object *obj); +void msm_gem_sync_cache (struct drm_gem_object *obj,uint32_t flags, +size_t range_start,size_t range_end);void msm_gem_free_object (struct drm_gem_object *obj);int msm_gem_new_handle (struct drm_device *dev,struct drm_file *file,uint32_t size,uint32_t flags,uint32_t *handle,char *name);
drivers/gpu/drm/msm/msm_gem.c +15 -0
@@ -8,6 +8,7 @@#include <linux/shmem_fs.h> #include <linux/dma-buf.h> #include <linux/pfn_t.h> +#include <linux/dma-noncoherent.h> #include <drm/drm_prime.h>
@@ -808,6 +809,20 @@ int msm_gem_cpu_fini(struct drm_gem_object *obj)return 0 ; } +void msm_gem_sync_cache (struct drm_gem_object *obj,uint32_t flags, +size_t range_start,size_t range_end) +{ +struct msm_gem_object *msm_obj =to_msm_bo (obj); + +/* TODO: sync only the required range, and don't invalidate on clean */ + +if (flags &MSM_GEM_SYNC_CACHE_CLEAN ) +sync_for_device (msm_obj); + +if (flags &MSM_GEM_SYNC_CACHE_INVALIDATE ) +sync_for_cpu (msm_obj); +} +#ifdef CONFIG_DEBUG_FS static void describe_fence (struct dma_fence *fence,const char *type,struct seq_file *m)
include/uapi/drm/msm_drm.h +20 -0
@@ -319,6 +319,24 @@ struct drm_msm_submitqueue_query {__u32 pad; }; +/* +* Host cache maintenance (relevant for MSM_BO_CACHED) +* driver may both clean/invalidate (flush) for clean +*/ + +#define MSM_GEM_SYNC_CACHE_CLEAN 0x1 +#define MSM_GEM_SYNC_CACHE_INVALIDATE 0x2 + +#define MSM_GEM_SYNC_CACHE_FLAGS (MSM_GEM_SYNC_CACHE_CLEAN | \ + MSM_GEM_SYNC_CACHE_INVALIDATE) + +struct drm_msm_gem_sync_cache { +__u32 handle; +__u32 flags; +__u64 offset; +__u64 end;/* offset + size */ +}; +#define DRM_MSM_GET_PARAM 0x00/* placeholder: #define DRM_MSM_SET_PARAM 0x01
@@ -336,6 +354,7 @@ struct drm_msm_submitqueue_query {#define DRM_MSM_SUBMITQUEUE_NEW 0x0A#define DRM_MSM_SUBMITQUEUE_CLOSE 0x0B#define DRM_MSM_SUBMITQUEUE_QUERY 0x0C +#define DRM_MSM_GEM_SYNC_CACHE 0x0D#define DRM_IOCTL_MSM_GET_PARAM DRM_IOWR(DRM_COMMAND_BASE + DRM_MSM_GET_PARAM, struct drm_msm_param)#define DRM_IOCTL_MSM_GEM_NEW DRM_IOWR(DRM_COMMAND_BASE + DRM_MSM_GEM_NEW, struct drm_msm_gem_new)
@@ -348,6 +367,7 @@ struct drm_msm_submitqueue_query {#define DRM_IOCTL_MSM_SUBMITQUEUE_NEW DRM_IOWR(DRM_COMMAND_BASE + DRM_MSM_SUBMITQUEUE_NEW, struct drm_msm_submitqueue)#define DRM_IOCTL_MSM_SUBMITQUEUE_CLOSE DRM_IOW (DRM_COMMAND_BASE + DRM_MSM_SUBMITQUEUE_CLOSE, __u32)#define DRM_IOCTL_MSM_SUBMITQUEUE_QUERY DRM_IOW (DRM_COMMAND_BASE + DRM_MSM_SUBMITQUEUE_QUERY, struct drm_msm_submitqueue_query) +#define DRM_IOCTL_MSM_GEM_SYNC_CACHE DRM_IOW (DRM_COMMAND_BASE + DRM_MSM_GEM_SYNC_CACHE, struct drm_msm_gem_sync_cache)#if defined(__cplusplus) }
Signature · 1 line
2.26.1
Re: [Freedreno] [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 78 lines · Jonathan Marek
This makes it possible to use the non-coherent cached
MSM_BO_CACHEDmode, which otherwise doesn't provide any method for cleaning/invalidating the cache to sync with the device.Signed-off-by Jonathan Marek <[email protected]>--- drivers/gpu/drm/msm/msm_drv.c | 21 +++++++++++++++++++++ drivers/gpu/drm/msm/msm_drv.h | 2 ++ drivers/gpu/drm/msm/msm_gem.c | 15 +++++++++++++++ include/uapi/drm/msm_drm.h | 20 ++++++++++++++++++++ 4 files changed, 58 insertions(+)drivers/gpu/drm/msm/msm_drv.c +21
-0@@ -964,6 +964,26 @@ static int msm_ioctl_submitqueue_close(struct drm_device *dev, void *data,return msm_submitqueue_remove (file->driver_priv, id); } +static int msm_ioctl_gem_sync_cache (struct drm_device *dev,void *data, +struct drm_file *file) +{ +struct drm_msm_gem_sync_cache *args = data; +struct drm_gem_object *obj; + +if (args->flags & ~MSM_GEM_SYNC_CACHE_FLAGS ) +return -EINVAL ; + + obj =drm_gem_object_lookup (file, args->handle); +if (!obj) +return -ENOENT ; + +msm_gem_sync_cache (obj, args->flags, args->offset, args->end); + +drm_gem_object_put (obj); + +return 0 ; +} +static const struct drm_ioctl_desc msm_ioctls[] = {DRM_IOCTL_DEF_DRV (MSM_GET_PARAM , msm_ioctl_get_param,DRM_RENDER_ALLOW ),DRM_IOCTL_DEF_DRV (MSM_GEM_NEW , msm_ioctl_gem_new,DRM_RENDER_ALLOW ),@@ -976,6 +996,7 @@ static const struct drm_ioctl_desc msm_ioctls[] = {DRM_IOCTL_DEF_DRV (MSM_SUBMITQUEUE_NEW , msm_ioctl_submitqueue_new,DRM_RENDER_ALLOW ),DRM_IOCTL_DEF_DRV (MSM_SUBMITQUEUE_CLOSE , msm_ioctl_submitqueue_close,DRM_RENDER_ALLOW ),DRM_IOCTL_DEF_DRV (MSM_SUBMITQUEUE_QUERY , msm_ioctl_submitqueue_query,DRM_RENDER_ALLOW ), + DRM_IOCTL_DEF_DRV(MSM_GEM_SYNC_CACHE, msm_ioctl_gem_sync_cache, DRM_RENDER_ALLOW), }; static const struct vm_operations_struct vm_ops = {drivers/gpu/drm/msm/msm_drv.h +2
-0@@ -314,6 +314,8 @@ void msm_gem_move_to_active(struct drm_gem_object *obj,void msm_gem_move_to_inactive (struct drm_gem_object *obj);int msm_gem_cpu_prep (struct drm_gem_object *obj,uint32_t op,ktime_t *timeout);int msm_gem_cpu_fini (struct drm_gem_object *obj); +void msm_gem_sync_cache (struct drm_gem_object *obj,uint32_t flags, +size_t range_start,size_t range_end);void msm_gem_free_object (struct drm_gem_object *obj);int msm_gem_new_handle (struct drm_device *dev,struct drm_file *file,uint32_t size,uint32_t flags,uint32_t *handle,char *name);drivers/gpu/drm/msm/msm_gem.c +1
-0@@ -8,6 +8,7 @@#include <linux/shmem_fs.h> #include <linux/dma-buf.h> #include <linux/pfn_t.h> +#include <linux/dma-noncoherent.h> #include <drm/drm_prime.h> @@ -808,6 +809,20 @@ int msm_gem_cpu_fini(struct drm_gem_object *obj)return 0 ;
drivers/gpu/drm/msm/msm_gem.c int msm_gem_cpu_fini(struct drm_gem_object *obj) · line 819
Quoted 10 lines
drivers/gpu/drm/msm/msm_gem.c +8
-0} +void msm_gem_sync_cache (struct drm_gem_object *obj,uint32_t flags, +size_t range_start,size_t range_end) +{ +struct msm_gem_object *msm_obj =to_msm_bo (obj); + +/* TODO: sync only the required range, and don't invalidate on clean */ + +if (flags &MSM_GEM_SYNC_CACHE_CLEAN )
Curious why you would rename these - I feel like the to_device / to_cpu model is pretty well baked into our thought process. I know from personal experience that I have to stop and think to remember which direction is which.
Jordan
Quoted 61 lines
drivers/gpu/drm/msm/msm_gem.c +6
-0+sync_for_device (msm_obj); + +if (flags &MSM_GEM_SYNC_CACHE_INVALIDATE ) +sync_for_cpu (msm_obj); +} +#ifdef CONFIG_DEBUG_FS static void describe_fence (struct dma_fence *fence,const char *type,struct seq_file *m)include/uapi/drm/msm_drm.h +20
-0@@ -319,6 +319,24 @@ struct drm_msm_submitqueue_query {__u32 pad; }; +/* +* Host cache maintenance (relevant for MSM_BO_CACHED) +* driver may both clean/invalidate (flush) for clean +*/ + +#define MSM_GEM_SYNC_CACHE_CLEAN 0x1 +#define MSM_GEM_SYNC_CACHE_INVALIDATE 0x2 + +#define MSM_GEM_SYNC_CACHE_FLAGS (MSM_GEM_SYNC_CACHE_CLEAN | \ + MSM_GEM_SYNC_CACHE_INVALIDATE) + +struct drm_msm_gem_sync_cache { +__u32 handle; +__u32 flags; +__u64 offset; +__u64 end;/* offset + size */ +}; +#define DRM_MSM_GET_PARAM 0x00/* placeholder: #define DRM_MSM_SET_PARAM 0x01 @@ -336,6 +354,7 @@ struct drm_msm_submitqueue_query {#define DRM_MSM_SUBMITQUEUE_NEW 0x0A#define DRM_MSM_SUBMITQUEUE_CLOSE 0x0B#define DRM_MSM_SUBMITQUEUE_QUERY 0x0C +#define DRM_MSM_GEM_SYNC_CACHE 0x0D#define DRM_IOCTL_MSM_GET_PARAM DRM_IOWR(DRM_COMMAND_BASE + DRM_MSM_GET_PARAM, struct drm_msm_param)#define DRM_IOCTL_MSM_GEM_NEW DRM_IOWR(DRM_COMMAND_BASE + DRM_MSM_GEM_NEW, struct drm_msm_gem_new)@@ -348,6 +367,7 @@ struct drm_msm_submitqueue_query {#define DRM_IOCTL_MSM_SUBMITQUEUE_NEW DRM_IOWR(DRM_COMMAND_BASE + DRM_MSM_SUBMITQUEUE_NEW, struct drm_msm_submitqueue)#define DRM_IOCTL_MSM_SUBMITQUEUE_CLOSE DRM_IOW (DRM_COMMAND_BASE + DRM_MSM_SUBMITQUEUE_CLOSE, __u32)#define DRM_IOCTL_MSM_SUBMITQUEUE_QUERY DRM_IOW (DRM_COMMAND_BASE + DRM_MSM_SUBMITQUEUE_QUERY, struct drm_msm_submitqueue_query) +#define DRM_IOCTL_MSM_GEM_SYNC_CACHE DRM_IOW (DRM_COMMAND_BASE + DRM_MSM_GEM_SYNC_CACHE, struct drm_msm_gem_sync_cache)#if defined(__cplusplus) }Signature · 6 lines
2.26.1 _______________________________________________ Freedreno mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/freedreno
Signature · 6 lines
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
In reply to Jonathan Marekdrivers/gpu/drm/msm/msm_gem.c line 11
Quoted 5 lines
drivers/gpu/drm/msm/msm_gem.c +1
-0@@ -8,6 +8,7 @@#include <linux/shmem_fs.h> #include <linux/dma-buf.h> #include <linux/pfn_t.h> +#include <linux/dma-noncoherent.h>
NAK, dma-noncoherent.h is not for driver use. And will in fact go away in 5.10.
Quoted 9 lines
drivers/gpu/drm/msm/msm_gem.c +2
-0#include <drm/drm_prime.h> @@ -808,6 +809,20 @@ int msm_gem_cpu_fini(struct drm_gem_object *obj)return 0 ; } +void msm_gem_sync_cache (struct drm_gem_object *obj,uint32_t flags, +size_t range_start,size_t range_end)
drivers/gpu/drm/msm/msm_gem.c int msm_gem_cpu_fini(struct drm_gem_object *obj) · line 823
Quoted 10 lines
drivers/gpu/drm/msm/msm_gem.c +10
-0+{ +struct msm_gem_object *msm_obj =to_msm_bo (obj); + +/* TODO: sync only the required range, and don't invalidate on clean */ + +if (flags &MSM_GEM_SYNC_CACHE_CLEAN ) +sync_for_device (msm_obj); + +if (flags &MSM_GEM_SYNC_CACHE_INVALIDATE ) +sync_for_cpu (msm_obj);
And make to these ones as well. They are complete abuses of the DMA API, and while we had to live with that for now to not cause regressions they absoutely must not be exposed in a userspace ABI like this.
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 9 lines · Christoph Hellwig
drivers/gpu/drm/msm/msm_gem.c line 11
Quoted 5 lines
drivers/gpu/drm/msm/msm_gem.c +1
-0@@ -8,6 +8,7 @@#include <linux/shmem_fs.h> #include <linux/dma-buf.h> #include <linux/pfn_t.h> +#include <linux/dma-noncoherent.h> NAK,
dma-noncoherent.his not for driver use. And will in fact go away in 5.10.
Not actually used, so can be removed.
Quoted 7 lines
Quoted 7 lines
drivers/gpu/drm/msm/msm_gem.c +0
-0#include <drm/drm_prime.h> @@ -808,6 +809,20 @@ int msm_gem_cpu_fini(struct drm_gem_object *obj)return 0 ; }
Quoted 17 lines
drivers/gpu/drm/msm/msm_gem.c int msm_gem_cpu_fini(struct drm_gem_object *obj) · line 823
Quoted 12 lines
drivers/gpu/drm/msm/msm_gem.c +12
-0+void msm_gem_sync_cache (struct drm_gem_object *obj,uint32_t flags, +size_t range_start,size_t range_end) +{ +struct msm_gem_object *msm_obj =to_msm_bo (obj); + +/* TODO: sync only the required range, and don't invalidate on clean */ + +if (flags &MSM_GEM_SYNC_CACHE_CLEAN ) +sync_for_device (msm_obj); + +if (flags &MSM_GEM_SYNC_CACHE_INVALIDATE ) +sync_for_cpu (msm_obj);And make to these ones as well. They are complete abuses of the DMA API, and while we had to live with that for now to not cause regressions they absoutely must not be exposed in a userspace ABI like this.
How do you propose that cached non-coherent memory be implemented? It is a useful feature for userspace.
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 18 lines · Jonathan Marek
Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/msm/msm_gem.c +8
-0+void msm_gem_sync_cache (struct drm_gem_object *obj,uint32_t flags, +size_t range_start,size_t range_end) +{ +struct msm_gem_object *msm_obj =to_msm_bo (obj); + +/* TODO: sync only the required range, and don't invalidate on clean */ + +if (flags &MSM_GEM_SYNC_CACHE_CLEAN )Quoted 9 lines
drivers/gpu/drm/msm/msm_gem.c int msm_gem_cpu_fini(struct drm_gem_object *obj) · line 823
Quoted 4 lines
drivers/gpu/drm/msm/msm_gem.c +4
-0+sync_for_device (msm_obj); + +if (flags &MSM_GEM_SYNC_CACHE_INVALIDATE ) +sync_for_cpu (msm_obj);And make to these ones as well. They are complete abuses of the DMA API, and while we had to live with that for now to not cause regressions they absoutely must not be exposed in a userspace ABI like this.
Quoted 2 lines
How do you propose that cached non-coherent memory be implemented? It is a useful feature for userspace.
If the driver is using the DMA API you need to use dma_alloc_noncoherent and friends as of 5.10 (see the iommu list for the discussion).
If you use the raw IOMMU API (which I think the msm drm driver does) you need to work with the maintainers to implement a cache synchronization API that is not tied to the DMA API.
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 22 lines · Christoph Hellwig
Quoted 18 lines · Jonathan Marek
Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/msm/msm_gem.c +8
-0+void msm_gem_sync_cache (struct drm_gem_object *obj,uint32_t flags, +size_t range_start,size_t range_end) +{ +struct msm_gem_object *msm_obj =to_msm_bo (obj); + +/* TODO: sync only the required range, and don't invalidate on clean */ + +if (flags &MSM_GEM_SYNC_CACHE_CLEAN )Quoted 9 lines
drivers/gpu/drm/msm/msm_gem.c int msm_gem_cpu_fini(struct drm_gem_object *obj) · line 823
Quoted 4 lines
drivers/gpu/drm/msm/msm_gem.c +4
-0+sync_for_device (msm_obj); + +if (flags &MSM_GEM_SYNC_CACHE_INVALIDATE ) +sync_for_cpu (msm_obj);And make to these ones as well. They are complete abuses of the DMA API, and while we had to live with that for now to not cause regressions they absoutely must not be exposed in a userspace ABI like this.
Quoted 2 lines
How do you propose that cached non-coherent memory be implemented? It is a useful feature for userspace.
Quoted 7 lines
If the driver is using the DMA API you need to use
dma_alloc_noncoherentand friends as of 5.10 (see the iommu list for the discussion).If you use the raw IOMMU API (which I think the msm drm driver does) you need to work with the maintainers to implement a cache synchronization API that is not tied to the DMA API.
The cache synchronization doesn't have anything to do with IOMMU (for example: cache synchronization would be useful in cases where drm/msm doesn't use IOMMU).
What is needed is to call arch_sync_dma_for_{cpu,device} (which is what I went with initially, but then decided to re-use drm/msm's sync_for_{cpu,device}). But you are also saying those functions aren't for driver use, and I doubt IOMMU maintainers will want to add wrappers for these functions just to satisfy this "not for driver use" requirement.
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 3 lines · Jonathan Marek
The cache synchronization doesn't have anything to do with IOMMU (for
example: cache synchronization would be useful in cases where drm/msm doesn't use IOMMU).
It has to do with doing DMA. And we have two frameworks for doing DMA:
either the DMA API which is for general driver use, and which as part of the design includes cache maintainance hidden behind the concept of ownership transfers. And we have the much more bare bones IOMMU API.
If people want to use the "raw" IOMMU API with not cache coherent devices we'll need a cache maintainance API that goes along with it. It could either be formally part of the IOMMU API or be separate.
Quoted 5 lines
What is needed is to call arch_sync_dma_for_{cpu,device} (which is what I went with initially, but then decided to re-use drm/msm's sync_for_{cpu,device}). But you are also saying those functions aren't for driver use, and I doubt IOMMU maintainers will want to add wrappers for these functions just to satisfy this "not for driver use" requirement.
arch_sync_dma_for_{cpu,device} are low-level helpers (and not very great ones at that). The definitively should not be used by drivers. They would be very useful buildblocks for a IOMMU cache maintainance API.
Of course the best outcome would be if we could find a way for the MSM drm driver to just use DMA API and not deal with the lower level abstractions. Do you remember why the driver went for use of the IOMMU API?
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 25 lines · Christoph Hellwig
Quoted 3 lines · Jonathan Marek
The cache synchronization doesn't have anything to do with IOMMU (for
example: cache synchronization would be useful in cases where drm/msm doesn't use IOMMU).It has to do with doing DMA. And we have two frameworks for doing DMA:
either the DMA API which is for general driver use, and which as part of the design includes cache maintainance hidden behind the concept of ownership transfers. And we have the much more bare bones IOMMU API.If people want to use the "raw" IOMMU API with not cache coherent devices we'll need a cache maintainance API that goes along with it. It could either be formally part of the IOMMU API or be separate.
Quoted 5 lines
What is needed is to call arch_sync_dma_for_{cpu,device} (which is what I went with initially, but then decided to re-use drm/msm's sync_for_{cpu,device}). But you are also saying those functions aren't for driver use, and I doubt IOMMU maintainers will want to add wrappers for these functions just to satisfy this "not for driver use" requirement.
arch_sync_dma_for_{cpu,device} are low-level helpers (and not very great ones at that). The definitively should not be used by drivers. They would be very useful buildblocks for a IOMMU cache maintainance API.
Quoted 5 lines
Of course the best outcome would be if we could find a way for the MSM drm driver to just use DMA API and not deal with the lower level abstractions. Do you remember why the driver went for use of the IOMMU API?
One example why drm/msm can't use DMA API is multiple page table support (that is landing in 5.10), which is something that definitely couldn't work with DMA API.
Another one is being able to choose the address for mappings, which AFAIK DMA API can't do (somewhat related to this: qcom hardware often has ranges of allowed addresses, which the dma_mask mechanism fails to represent, what I see is drivers using dma_mask as a "maximum address", and since addresses are allocated from the top it generally works)
But let us imagine drm/msm switches to using DMA API. a2xx GPUs have their own very basic MMU (implemented by msm_gpummu.c), that will need to implement dma_map_ops, which will have to call arch_sync_dma_for_{cpu,device}. So drm/msm still needs to call arch_sync_dma_for_{cpu,device} in that scenario.
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 9 lines · Jonathan Marek
One example why drm/msm can't use DMA API is multiple page table support (that is landing in 5.10), which is something that definitely couldn't work with DMA API.
Another one is being able to choose the address for mappings, which AFAIK DMA API can't do (somewhat related to this: qcom hardware often has ranges of allowed addresses, which the
dma_maskmechanism fails to represent, what I see is drivers usingdma_maskas a "maximum address", and since addresses are allocated from the top it generally works)
That sounds like a good enough rason to use the IOMMU API. I just wanted to make sure this really makes sense.
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 5 lines · Christoph Hellwig
Quoted 4 lines · Jonathan Marek
One example why drm/msm can't use DMA API is multiple page table support (that is landing in 5.10), which is something that definitely couldn't work with DMA API.
Quoted 8 lines
Quoted 5 lines
Another one is being able to choose the address for mappings, which AFAIK DMA API can't do (somewhat related to this: qcom hardware often has ranges of allowed addresses, which the
dma_maskmechanism fails to represent, what I see is drivers usingdma_maskas a "maximum address", and since addresses are allocated from the top it generally works)That sounds like a good enough rason to use the IOMMU API. I just wanted to make sure this really makes sense.
I still think this situation would be best handled with a variant of dma_ops_bypass that also guarantees to bypass SWIOTLB, and can be set automatically when attaching to an unmanaged IOMMU domain. That way the device driver can make DMA API calls in the appropriate places that do the right thing either way, and only needs logic to decide whether to use the returned DMA addresses directly or ignore them if it knows they're overridden by its own IOMMU mapping.
Robin.
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 16 lines · Robin Murphy
Quoted 5 lines · Christoph Hellwig
Quoted 4 lines · Jonathan Marek
One example why drm/msm can't use DMA API is multiple page table support (that is landing in 5.10), which is something that definitely couldn't work with DMA API.
Quoted 8 lines
Quoted 5 lines
Another one is being able to choose the address for mappings, which AFAIK DMA API can't do (somewhat related to this: qcom hardware often has ranges of allowed addresses, which the
dma_maskmechanism fails to represent, what I see is drivers usingdma_maskas a "maximum address", and since addresses are allocated from the top it generally works)That sounds like a good enough rason to use the IOMMU API. I just wanted to make sure this really makes sense.
Quoted 8 lines
I still think this situation would be best handled with a variant of
dma_ops_bypassthat also guarantees to bypass SWIOTLB, and can be set automatically when attaching to an unmanaged IOMMU domain. That way the device driver can make DMA API calls in the appropriate places that do the right thing either way, and only needs logic to decide whether to use the returned DMA addresses directly or ignore them if it knows they're overridden by its own IOMMU mapping.
That would be pretty ideal from my PoV
BR,
-R
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
In reply to Robin MurphyQuoted 3 lines · Robin Murphy
I still think this situation would be best handled with a variant of
dma_ops_bypassthat also guarantees to bypass SWIOTLB, and can be set automatically when attaching to an unmanaged IOMMU domain.
dma_ops_bypass should mostly do the right thing as-is. swiotlb bouncing is triggered of two things:
1) the dma_mask. This is under control of the driver, and obviously if it is too small for a legit reason we can't just proceed
2) force_dma_unencrypted() - we'd need to do an opt-out here, either by a flag or by being smart and looking for an attached iommu on the device
Quoted 5 lines
That way the
device driver can make DMA API calls in the appropriate places that do the right thing either way, and only needs logic to decide whether to use the returned DMA addresses directly or ignore them if it knows they're overridden by its own IOMMU mapping.
I'd be happy to review patches for this.
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 10 lines · Christoph Hellwig
Quoted 3 lines · Robin Murphy
I still think this situation would be best handled with a variant of
dma_ops_bypassthat also guarantees to bypass SWIOTLB, and can be set automatically when attaching to an unmanaged IOMMU domain.
dma_ops_bypassshould mostly do the right thing as-is. swiotlb bouncing is triggered of two things:1) the
dma_mask. This is under control of the driver, and obviously if it is too small for a legit reason we can't just proceed
Somewhat related, but is there a way to tell the dma-api to fail instead of falling back to swiotlb? In many case for gpu drivers it's much better if we fall back to dma_alloc_coherent and manage the copying ourselves instead of abstracting this away in the dma-api. Currently that's "solved" rather pessimistically by always allocating from dma_alloc_coherent if swiotlb could be in the picture (at least for ttm based drivers, i915 just falls over).
-Daniel
Quoted 11 lines
2)
force_dma_unencrypted()- we'd need to do an opt-out here, either by a flag or by being smart and looking for an attached iommu on the deviceQuoted 5 lines
That way the
device driver can make DMA API calls in the appropriate places that do the right thing either way, and only needs logic to decide whether to use the returned DMA addresses directly or ignore them if it knows they're overridden by its own IOMMU mapping.I'd be happy to review patches for this.
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 12 lines · Daniel Vetter
Quoted 10 lines · Christoph Hellwig
Quoted 3 lines · Robin Murphy
I still think this situation would be best handled with a variant of
dma_ops_bypassthat also guarantees to bypass SWIOTLB, and can be set automatically when attaching to an unmanaged IOMMU domain.
dma_ops_bypassshould mostly do the right thing as-is. swiotlb bouncing is triggered of two things:1) the
dma_mask. This is under control of the driver, and obviously if it is too small for a legit reason we can't just proceed
Quoted 7 lines
Somewhat related, but is there a way to tell the dma-api to fail instead of falling back to swiotlb? In many case for gpu drivers it's much better if we fall back to
dma_alloc_coherentand manage the copying ourselves instead of abstracting this away in the dma-api. Currently that's "solved" rather pessimistically by always allocating fromdma_alloc_coherentif swiotlb could be in the picture (at least for ttm based drivers, i915 just falls over).
Is this for the alloc_pages plus manually map logic in various drivers?
They should switch to the new dma_alloc_pages API that I'll send to Linus for 5.10 soon.
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
Quoted 8 lines · Christoph Hellwig
Quoted 7 lines
Somewhat related, but is there a way to tell the dma-api to fail instead of falling back to swiotlb? In many case for gpu drivers it's much better if we fall back to
dma_alloc_coherentand manage the copying ourselves instead of abstracting this away in the dma-api. Currently that's "solved" rather pessimistically by always allocating fromdma_alloc_coherentif swiotlb could be in the picture (at least for ttm based drivers, i915 just falls over).
Quoted 4 lines
Is this for the
alloc_pagesplus manually map logic in various drivers?They should switch to the new
dma_alloc_pagesAPI that I'll send to Linus for 5.10 soon.
Daniel, can you clarify this?
Re: [PATCH 2/3] drm/msm: add DRM_MSM_GEM_SYNC_CACHE for non-coherent cache maintenance
In reply to Christoph HellwigQuoted 3 lines · Christoph Hellwig
If people want to use the "raw" IOMMU API with not cache coherent devices we'll need a cache maintainance API that goes along with it. It could either be formally part of the IOMMU API or be separate.
The IOMMU-API does not care about the caching effects of DMA, is manages IO address spaces for devices. I also don't know how this would be going to be implemented, the IOMMU-API does not have the concept of handles for mapped ranges and does not care about CPU virtual addresses (which are needed for cache flushes) of the memory it maps into IO page-tables.
So I think a cache management API should be separate from the IOMMU-API.
Regards,
Joerg
PATCH 3/3 drm/msm: bump up the uapi version
In reply to Jonathan MarekIncrease the minor version to indicate the presence of new features.
--- drivers/gpu/drm/msm/msm_drv.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/msm/msm_drv.c +2 -1
@@ -38,9 +38,10 @@* GEM object's debug name * - 1.5.0 - Add SUBMITQUERY_QUERY ioctl * - 1.6.0 - Syncobj support +* - 1.7.0 - MSM_BO_CACHED_COHERENT and DRM_IOCTL_MSM_GEM_SYNC_CACHE */ #define MSM_VERSION_MAJOR 1 -#define MSM_VERSION_MINOR 6 +#define MSM_VERSION_MINOR 7#define MSM_VERSION_PATCHLEVEL 0static const struct drm_mode_config_funcs mode_config_funcs = {
Signature · 1 line
2.26.1