Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: priyanka.dandamudi@intel.com, igt-dev@lists.freedesktop.org,
	arjun.melkaveri@intel.com,
	John Harrison <john.c.harrison@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 3/4] lib/igt_gt: Add compute engine
Date: Thu, 21 Oct 2021 17:12:26 -0700	[thread overview]
Message-ID: <87y26l9atx.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20211021073321.GC3640@zkempczy-mobl2>

On Thu, 21 Oct 2021 00:33:21 -0700, Zbigniew Kempczyński wrote:
>
> On Thu, Oct 21, 2021 at 10:05:07AM +0530, priyanka.dandamudi@intel.com wrote:
> > From: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> >
> > Add compute (CCS) engine. Add this to the IGT
> > structure to allow gem tests to execute.
> >
> > Signed-off-by: Stuart Summers <stuart.summers@intel.com>
> > Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> > Signed-off-by: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
> > Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > Cc: Arjun Melkaveri <arjun.melkaveri@intel.com>
> > ---
> >  lib/igt_gt.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/lib/igt_gt.c b/lib/igt_gt.c
> > index a0ba04cc..80fb65ca 100644
> > --- a/lib/igt_gt.c
> > +++ b/lib/igt_gt.c
> > @@ -604,6 +604,10 @@ const struct intel_execution_engine2 intel_execution_engines2[] = {
> >	{ "vcs1", I915_ENGINE_CLASS_VIDEO, 1, I915_EXEC_BSD | I915_EXEC_BSD_RING2 },
> >	{ "vcs2", I915_ENGINE_CLASS_VIDEO, 2, -1 },
> >	{ "vecs0", I915_ENGINE_CLASS_VIDEO_ENHANCE, 0, I915_EXEC_VEBOX },
> > +	{ "ccs0", I915_ENGINE_CLASS_COMPUTE, 0 , -1},
> > +	{ "ccs1", I915_ENGINE_CLASS_COMPUTE, 1 , -1},
> > +	{ "ccs2", I915_ENGINE_CLASS_COMPUTE, 2 , -1},
> > +	{ "ccs3", I915_ENGINE_CLASS_COMPUTE, 3 , -1},
>
> LGTM,
>
> Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>

Is this correct? Isn't intel_execution_engines2 a list of just the legacy
engines? I don't think compute engines (which may vary in number) can be
added to the list of legacy engines. Isn't it true that compute engines can
only be accessed by querying the present engines dynamically (using
something like intel_ctx_create_all_physical())?

For example see:

/**
 * __for_each_static_engine:
 * @e__: struct intel_execution_engine2 iterator
 *
 * Iterates over each of the statically defined (legacy) engines.
 */
#define __for_each_static_engine(e__) \
        for ((e__) = intel_execution_engines2; (e__)->name[0]; (e__)++)

  reply	other threads:[~2021-10-22  0:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21  4:35 [igt-dev] [PATCH i-g-t 0/4] CCS engine and engine resets test priyanka.dandamudi
2021-10-21  4:35 ` [igt-dev] [PATCH i-g-t 1/4] i915/gem_engine_topology: Add compute class priyanka.dandamudi
2021-10-21  7:18   ` Zbigniew Kempczyński
2021-10-21  4:35 ` [igt-dev] [PATCH i-g-t 2/4] tests/gem_ctx_persistence: Update saturated_hostile for dependent engine resets priyanka.dandamudi
2021-10-21 21:11   ` Matthew Brost
2021-10-21  4:35 ` [igt-dev] [PATCH i-g-t 3/4] lib/igt_gt: Add compute engine priyanka.dandamudi
2021-10-21  7:33   ` Zbigniew Kempczyński
2021-10-22  0:12     ` Dixit, Ashutosh [this message]
2021-10-22  0:29       ` Dixit, Ashutosh
2021-10-22  4:40         ` Zbigniew Kempczyński
2021-10-22 12:07           ` Tvrtko Ursulin
2021-10-22 23:36             ` Dixit, Ashutosh
2021-10-23  0:15             ` Dixit, Ashutosh
2021-10-25 22:35               ` Dixit, Ashutosh
2021-10-25  3:50             ` Zbigniew Kempczyński
2021-10-21  4:35 ` [igt-dev] [PATCH i-g-t 4/4] lib/i915/i915_drm_local: Add COMPUTE class engine priyanka.dandamudi
2021-10-21  7:17   ` Zbigniew Kempczyński
2021-10-21  5:26 ` [igt-dev] ✓ Fi.CI.BAT: success for CCS engine and engine resets test Patchwork
2021-10-21  8:03 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=87y26l9atx.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=arjun.melkaveri@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=john.c.harrison@intel.com \
    --cc=priyanka.dandamudi@intel.com \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=zbigniew.kempczynski@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