public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Introduce struct class_instance for engines across the uAPI
Date: Fri, 12 Apr 2019 08:02:04 +0100	[thread overview]
Message-ID: <1bc88e92-9164-fd10-95ad-856705a985a7@linux.intel.com> (raw)
In-Reply-To: <20190412065147.25144-1-chris@chris-wilson.co.uk>


+Tony to comment on the media-driver views on this.

+Manually re-adding original Cc which did not appear for me from the ML.

On 12/04/2019 07:51, Chris Wilson wrote:
> SSEU reprogramming of the context introduced the notion of engine class
> and instance for a forwards compatible method of describing any engine
> beyond the old execbuf interface. We wish to adopt this class:instance
> description for more interfaces, so pull it out into a separate type for
> userspace convenience.
> 
> References: e46c2e99f600 ("drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only)")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Cc: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
> Cc: Andi Shyti <andi@etezian.org>
> ---
> Commit e46c2e99f600 ("drm/i915: Expose RPCS (SSEU) configuration to
> userspace (Gen11 only)") is for v5.1, so we still do have a tiny bit of
> time to enact this change.
> ---
>   drivers/gpu/drm/i915/i915_gem_context.c |  8 ++++----
>   include/uapi/drm/i915_drm.h             | 11 +++++++++--
>   2 files changed, 13 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
> index 7fc34ab6df87..dd728b26b5aa 100644
> --- a/drivers/gpu/drm/i915/i915_gem_context.c
> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
> @@ -1386,8 +1386,8 @@ static int set_sseu(struct i915_gem_context *ctx,
>   		return -EINVAL;
>   
>   	engine = intel_engine_lookup_user(i915,
> -					  user_sseu.engine_class,
> -					  user_sseu.engine_instance);
> +					  user_sseu.engine.engine_class,
> +					  user_sseu.engine.engine_instance);
>   	if (!engine)
>   		return -EINVAL;
>   
> @@ -1626,8 +1626,8 @@ static int get_sseu(struct i915_gem_context *ctx,
>   		return -EINVAL;
>   
>   	engine = intel_engine_lookup_user(ctx->i915,
> -					  user_sseu.engine_class,
> -					  user_sseu.engine_instance);
> +					  user_sseu.engine.engine_class,
> +					  user_sseu.engine.engine_instance);
>   	if (!engine)
>   		return -EINVAL;
>   
> diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h
> index 52051d24d89d..f6369c462458 100644
> --- a/include/uapi/drm/i915_drm.h
> +++ b/include/uapi/drm/i915_drm.h
> @@ -1500,6 +1500,14 @@ struct drm_i915_gem_context_param {
>   	__u64 value;
>   };
>   
> +union drm_i915_engine_class_instance {
> +	struct i915_engine_class_instance {
> +		__u16 engine_class;
> +		__u16 engine_instance;
> +	} class_instance;
> +	__u32 ci;

Is "ci" class instance or something to satisfy the test farm and what is 
the purpose for the union?

> +};
> +
>   /**
>    * Context SSEU programming
>    *
> @@ -1525,8 +1533,7 @@ struct drm_i915_gem_context_param_sseu {
>   	/*
>   	 * Engine class & instance to be configured or queried.
>   	 */
> -	__u16 engine_class;
> -	__u16 engine_instance;
> +	struct i915_engine_class_instance engine;
>   
>   	/*
>   	 * Unused for now. Must be cleared to zero.
> 

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-04-12  7:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12  6:51 [PATCH] drm/i915: Introduce struct class_instance for engines across the uAPI Chris Wilson
2019-04-12  7:02 ` Tvrtko Ursulin [this message]
2019-04-12  7:07   ` Chris Wilson
2019-04-12  7:10 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-04-12  7:14 ` [PATCH v2] " Chris Wilson
2019-04-12 12:10   ` Tvrtko Ursulin
2019-04-12 14:17     ` Ye, Tony
2019-04-12  8:48 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Introduce struct class_instance for engines across the uAPI (rev2) Patchwork
2019-04-12 11:36 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-04-29 17:08 ` [PATCH] drm/i915: Introduce struct class_instance for engines across the uAPI Rodrigo Vivi
2019-05-01  9:50   ` Chris Wilson

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=1bc88e92-9164-fd10-95ad-856705a985a7@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox