From: Oscar Mateo <oscar.mateo@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 4/5] drm/i915: Split the engine info table in two levels, using class + instance
Date: Thu, 6 Apr 2017 06:29:39 -0700 [thread overview]
Message-ID: <4315f3fa-fd92-d1a2-276f-9b6bb0ffc2b9@intel.com> (raw)
In-Reply-To: <20170406201226.GQ10496@nuc-i3427.alporthouse.com>
On 04/06/2017 01:12 PM, Chris Wilson wrote:
> On Thu, Apr 06, 2017 at 05:55:43AM -0700, Oscar Mateo wrote:
>> There are some properties that logically belong to the engine class, and some
>> that belong to the engine instance. Make it explicit.
>>
>> v2: Commit message (Tvrtko)
>>
>> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Signed-off-by: Oscar Mateo <oscar.mateo@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_engine_cs.c | 72 +++++++++++++++++++++-------------
>> 1 file changed, 44 insertions(+), 28 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c b/drivers/gpu/drm/i915/intel_engine_cs.c
>> index 2409908..506ec952 100644
>> --- a/drivers/gpu/drm/i915/intel_engine_cs.c
>> +++ b/drivers/gpu/drm/i915/intel_engine_cs.c
>> @@ -26,71 +26,83 @@
>> #include "intel_ringbuffer.h"
>> #include "intel_lrc.h"
>>
>> -static const struct engine_info {
>> +struct engine_class_info {
>> const char *name;
>> unsigned int exec_id;
> Ugh. What??? Each engine will have a unique exec/uabi id.
> -Chris
Ok, I'll move it back to the instance if it matches better the VLC load
balancing work?
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-04-06 20:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 12:55 [PATCH 0/5] Classify the engines in class + instance (v2) Oscar Mateo
2017-04-06 12:55 ` [PATCH 1/5] drm/i915: Classify the engines in class + instance Oscar Mateo
2017-04-06 12:55 ` [PATCH 2/5] drm/i915: Use the same vfunc for BSD2 ring init Oscar Mateo
2017-04-06 12:55 ` [PATCH 3/5] drm/i915: Generate the engine name based on the instance number Oscar Mateo
2017-04-06 20:10 ` Chris Wilson
2017-04-06 13:15 ` Oscar Mateo
2017-04-06 13:36 ` [PATCH v3] " Oscar Mateo
2017-04-06 12:55 ` [PATCH 4/5] drm/i915: Split the engine info table in two levels, using class + instance Oscar Mateo
2017-04-06 20:12 ` Chris Wilson
2017-04-06 13:29 ` Oscar Mateo [this message]
2017-04-06 12:55 ` [PATCH 5/5] drm/i915: Use the engine class to get the context size Oscar Mateo
2017-04-06 20:30 ` ✓ Fi.CI.BAT: success for Classify the engines in class + instance (rev2) Patchwork
2017-04-06 20:40 ` ✗ Fi.CI.BAT: failure for Classify the engines in class + instance (rev3) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-04-10 14:34 [PATCH 0/5] Classify the engines in class + instance (v5) Oscar Mateo
2017-04-10 14:34 ` [PATCH 4/5] drm/i915: Split the engine info table in two levels, using class + instance Oscar Mateo
2017-04-11 11:35 ` Tvrtko Ursulin
2017-04-07 9:15 [PATCH 0/5] Classify the engines in class + instance (v4) Oscar Mateo
2017-04-07 9:15 ` [PATCH 4/5] drm/i915: Split the engine info table in two levels, using class + instance Oscar Mateo
2017-04-07 16:27 ` Michal Wajdeczko
2017-04-06 15:00 [PATCH 0/5] Classify the engines in class + instance (v3) Oscar Mateo
2017-04-06 15:00 ` [PATCH 4/5] drm/i915: Split the engine info table in two levels, using class + instance Oscar Mateo
2017-04-07 8:14 ` Tvrtko Ursulin
2017-04-07 10:43 ` Michal Wajdeczko
2017-04-05 9:30 [PATCH 0/5] Classify the engines in " Oscar Mateo
2017-04-05 9:30 ` [PATCH 4/5] drm/i915: Split the engine info table in two levels, using " Oscar Mateo
2017-04-06 18:09 ` Tvrtko Ursulin
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=4315f3fa-fd92-d1a2-276f-9b6bb0ffc2b9@intel.com \
--to=oscar.mateo@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@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