From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Tvrtko Ursulin <tursulin@ursulin.net>
Subject: Re: [PATCH] drm/i915/gt: Refactor uabi engine class/instance list creation
Date: Tue, 23 Apr 2024 11:02:06 +0200 [thread overview]
Message-ID: <3e69af0e-11e5-4bfc-8400-8ebbec7d34ef@linux.intel.com> (raw)
In-Reply-To: <20240416224953.385726-1-andi.shyti@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 3381 bytes --]
Hi Andi,
On 4/17/2024 12:49 AM, Andi Shyti wrote:
> For the upcoming changes we need a cleaner way to build the list
> of uabi engines.
>
> Suggested-by: Tvrtko Ursulin<tvrtko.ursulin@intel.com>
> Signed-off-by: Andi Shyti<andi.shyti@linux.intel.com>
> ---
> Hi,
>
> just sending this patch to unburden the coming series from this
> single patch inherited from a previously sent series.
>
> Andi
>
> drivers/gpu/drm/i915/gt/intel_engine_user.c | 29 ++++++++++++---------
> 1 file changed, 17 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_user.c b/drivers/gpu/drm/i915/gt/intel_engine_user.c
> index 833987015b8b..11cc06c0c785 100644
> --- a/drivers/gpu/drm/i915/gt/intel_engine_user.c
> +++ b/drivers/gpu/drm/i915/gt/intel_engine_user.c
> @@ -203,7 +203,7 @@ static void engine_rename(struct intel_engine_cs *engine, const char *name, u16
>
> void intel_engines_driver_register(struct drm_i915_private *i915)
> {
> - u16 name_instance, other_instance = 0;
> + u16 class_instance[I915_LAST_UABI_ENGINE_CLASS + 2] = { };
+2 is confusing here. I think we need a better macro.
> struct legacy_ring ring = {};
> struct list_head *it, *next;
> struct rb_node **p, *prev;
> @@ -214,6 +214,8 @@ void intel_engines_driver_register(struct drm_i915_private *i915)
> prev = NULL;
> p = &i915->uabi_engines.rb_node;
> list_for_each_safe(it, next, &engines) {
> + u16 uabi_class;
> +
> struct intel_engine_cs *engine =
> container_of(it, typeof(*engine), uabi_list);
>
> @@ -222,15 +224,14 @@ void intel_engines_driver_register(struct drm_i915_private *i915)
>
> GEM_BUG_ON(engine->class >= ARRAY_SIZE(uabi_classes));
> engine->uabi_class = uabi_classes[engine->class];
> - if (engine->uabi_class == I915_NO_UABI_CLASS) {
> - name_instance = other_instance++;
> - } else {
> - GEM_BUG_ON(engine->uabi_class >=
> - ARRAY_SIZE(i915->engine_uabi_class_count));
> - name_instance =
> - i915->engine_uabi_class_count[engine->uabi_class]++;
> - }
> - engine->uabi_instance = name_instance;
> +
> + if (engine->uabi_class == I915_NO_UABI_CLASS)
> + uabi_class = I915_LAST_UABI_ENGINE_CLASS + 1;
> + else
> + uabi_class = engine->uabi_class;
> +
> + GEM_BUG_ON(uabi_class >= ARRAY_SIZE(class_instance));
> + engine->uabi_instance = class_instance[uabi_class]++;
>
> /*
> * Replace the internal name with the final user and log facing
> @@ -238,11 +239,15 @@ void intel_engines_driver_register(struct drm_i915_private *i915)
> */
> engine_rename(engine,
> intel_engine_class_repr(engine->class),
> - name_instance);
> + engine->uabi_instance);
>
> - if (engine->uabi_class == I915_NO_UABI_CLASS)
> + if (uabi_class > I915_LAST_UABI_ENGINE_CLASS)
> continue;
>
> + GEM_BUG_ON(uabi_class >=
> + ARRAY_SIZE(i915->engine_uabi_class_count));
> + i915->engine_uabi_class_count[uabi_class]++;
Shouldn't this be i915->engine_uabi_class_count[uabi_class] =
class_instance[uabi_class]; ?
What I see is that this patch mainly adding this class_instance array
and rest looks the same.
May be it make sense to add other upcoming patches to better understand
why we need this patch.
Regards,
Nirmoy
> +
> rb_link_node(&engine->uabi_node, prev, p);
> rb_insert_color(&engine->uabi_node, &i915->uabi_engines);
>
[-- Attachment #2: Type: text/html, Size: 4298 bytes --]
next prev parent reply other threads:[~2024-04-23 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 22:49 [PATCH] drm/i915/gt: Refactor uabi engine class/instance list creation Andi Shyti
2024-04-16 23:37 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-04-16 23:44 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-17 7:20 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-18 16:28 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt: Refactor uabi engine class/instance list creation (rev2) Patchwork
2024-04-18 16:41 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-23 9:02 ` Nirmoy Das [this message]
2024-04-23 10:05 ` [PATCH] drm/i915/gt: Refactor uabi engine class/instance list creation Andi Shyti
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=3e69af0e-11e5-4bfc-8400-8ebbec7d34ef@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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