From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Drop verbose and archaic "ring" from our internal engine names
Date: Thu, 30 Mar 2017 15:23:25 +0300 [thread overview]
Message-ID: <1490876605.3067.8.camel@linux.intel.com> (raw)
In-Reply-To: <20170329220407.30642-1-chris@chris-wilson.co.uk>
On ke, 2017-03-29 at 23:04 +0100, Chris Wilson wrote:
> We pretty print the name of an engine in several places, mostly for
> debug, but also in the GPU hang report. Using "ring" in the name is
> archaic (we call those engines now to differentiate them from the
> multiple rings of commands we execute on each engine), quite verbose and
> often tautological. We run out of room in our GPU hang report for
> instance if we have more than a couple of engines hung simultaneously.
> Bit the bullet and update the strings to reflect the common internal names.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
<SNIP>
> @@ -36,7 +36,7 @@ static const struct engine_info {
> int (*init_execlists)(struct intel_engine_cs *engine);
> } intel_engines[] = {
> [RCS] = {
> - .name = "render ring",
> + .name = "rcs",
> .uabi_id = I915_EXEC_RENDER,
> .hw_id = RCS_HW,
Lift the .hw_id after .name now that it's the more closely related.
With that applied to each;
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-30 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 22:04 [PATCH] drm/i915: Drop verbose and archaic "ring" from our internal engine names Chris Wilson
2017-03-30 12:23 ` Joonas Lahtinen [this message]
2017-03-30 13:29 ` Tvrtko Ursulin
2017-03-31 7:59 ` Mika Kuoppala
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=1490876605.3067.8.camel@linux.intel.com \
--to=joonas.lahtinen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.