From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v1 1/8] drm/xe: Extend drm_xe_vm_bind_op
Date: Thu, 16 Nov 2023 15:57:38 -0500 [thread overview]
Message-ID: <ZVaCQlfHCfblg8ux@intel.com> (raw)
In-Reply-To: <20231116144316.7-2-francois.dugast@intel.com>
On Thu, Nov 16, 2023 at 02:43:09PM +0000, Francois Dugast wrote:
> From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>
> The bind api is extensible but for a single bind op, there
> is not a mechanism to extend. Add extensions field to
> struct drm_xe_vm_bind_op.
>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: Francois Dugast <francois.dugast@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Dominik Grzegorzek <dominik.grzegorzek@intel.com>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> include/uapi/drm/xe_drm.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
> index d66e8dc72e96..eb53c7a367a1 100644
> --- a/include/uapi/drm/xe_drm.h
> +++ b/include/uapi/drm/xe_drm.h
> @@ -613,6 +613,9 @@ struct drm_xe_vm_destroy {
> };
>
> struct drm_xe_vm_bind_op {
> + /** @extensions: Pointer to the first extension struct, if any */
> + __u64 extensions;
> +
> /**
> * @obj: GEM object to operate on, MBZ for MAP_USERPTR, MBZ for UNMAP
> */
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-11-16 20:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 14:43 [Intel-xe] [PATCH v1 0/8] uAPI Alignment - Cleanup and future proof Francois Dugast
2023-11-16 14:43 ` [Intel-xe] [PATCH v1 1/8] drm/xe: Extend drm_xe_vm_bind_op Francois Dugast
2023-11-16 20:57 ` Rodrigo Vivi [this message]
2023-11-16 14:43 ` [Intel-xe] [PATCH v1 2/8] drm/xe/uapi: Separate bo_create placement from flags Francois Dugast
2023-11-16 14:43 ` [Intel-xe] [PATCH v1 3/8] drm/xe: Make DRM_XE_DEVICE_QUERY_ENGINES future proof Francois Dugast
2023-11-16 14:43 ` [Intel-xe] [PATCH v1 4/8] drm/xe/uapi: Reject bo creation of unaligned size Francois Dugast
2023-11-16 14:43 ` [Intel-xe] [PATCH v1 5/8] drm/xe/uapi: Align on a common way to return arrays (memory regions) Francois Dugast
2023-11-16 20:39 ` Souza, Jose
2023-11-16 14:43 ` [Intel-xe] [PATCH v1 6/8] drm/xe/uapi: Align on a common way to return arrays (gt) Francois Dugast
2023-11-16 20:40 ` Souza, Jose
2023-11-16 20:56 ` Rodrigo Vivi
2023-11-16 21:28 ` Matt Roper
2023-11-16 14:43 ` [Intel-xe] [PATCH v1 7/8] drm/xe/uapi: Align on a common way to return arrays (engines) Francois Dugast
2023-11-16 20:42 ` Souza, Jose
2023-11-16 14:43 ` [Intel-xe] [PATCH v1 8/8] drm/xe/uapi: Add Tile ID information to the GT info query Francois Dugast
2023-11-16 20:44 ` Souza, Jose
2023-11-16 20:52 ` Rodrigo Vivi
2023-11-16 20:54 ` Souza, Jose
2023-11-17 4:06 ` [Intel-xe] [PATCH] drm/xe/uapi: Fix various struct padding for 64b alignment Rodrigo Vivi
2023-11-17 14:25 ` Souza, Jose
2023-11-17 16:24 ` Matt Roper
2023-11-16 14:46 ` [Intel-xe] ✗ CI.Patch_applied: failure for uAPI Alignment - Cleanup and future proof Patchwork
2023-11-18 3:14 ` [Intel-xe] ✓ CI.Patch_applied: success " Patchwork
2023-11-18 3:14 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-11-18 3:15 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-11-18 3:23 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-18 3:23 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-11-18 3:24 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-11-18 3:59 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-11-20 12:44 ` [Intel-xe] ✗ CI.Patch_applied: failure for uAPI Alignment - Cleanup and future proof (rev3) Patchwork
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=ZVaCQlfHCfblg8ux@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox