[PATCH] drm/xe/uapi: Add documentation for DRM_XE_GEM_CREATE_FLAG_DEFER_BACKING
Lucas De Marchi
lucas.demarchi at intel.com
Thu Jul 24 15:00:25 UTC 2025
On Thu, Jul 24, 2025 at 11:36:10AM +0530, priyanka.dandamudi at intel.com wrote:
>From: Priyanka Dandamudi <priyanka.dandamudi at intel.com>
>
>Add documentation for drm_xe_gem_create structure flag
>DRM_XE_GEM_CREATE_FLAG_DEFER_BACKING.
>
>v2: Modified to be in a more generalised way.
>
>Signed-off-by: Priyanka Dandamudi <priyanka.dandamudi at intel.com>
>---
> include/uapi/drm/xe_drm.h | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
>diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
>index e2426413488f..2ceafa5305d2 100644
>--- a/include/uapi/drm/xe_drm.h
>+++ b/include/uapi/drm/xe_drm.h
>@@ -760,7 +760,11 @@ struct drm_xe_device_query {
> * gem creation
> *
> * The @flags can be:
>- * - %DRM_XE_GEM_CREATE_FLAG_DEFER_BACKING
>+ * - %DRM_XE_GEM_CREATE_FLAG_DEFER_BACKING - This flag modifies the GEM
^^^^^^^^^^^^^^^^^^
This makes it too verbose and is not the style used in other flags.
%DRM_XE_GEM_CREATE_FLAG_NEEDS_VISIBLE_VRAM - When using VRAM as a possible placement, ensure ...
%DRM_XE_GEM_CPU_CACHING_WB - Allocate ...
%DRM_XE_GEM_CPU_CACHING_WC - Allocate ...
Here it could be:
%DRM_XE_GEM_CREATE_FLAG_DEFER_BACKING - Modify the GEM ...
>+ * object allocation strategy by deferring physical memory allocation
>+ * until the object is either bound to a virtual memory region via
>+ * VM_BIND or accessed by the CPU. As a result, no backing memory is
>+ * reserved at the time of GEM object creation.
with the change above, Reviewed-by: Lucas De Marchi <lucas.demarchi at intel.com>
thanks
Lucas De Marchi
> * - %DRM_XE_GEM_CREATE_FLAG_SCANOUT
> * - %DRM_XE_GEM_CREATE_FLAG_NEEDS_VISIBLE_VRAM - When using VRAM as a
> * possible placement, ensure that the corresponding VRAM allocation
>--
>2.34.1
>
More information about the Intel-xe
mailing list