All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti via igt-dev <igt-dev@lists.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: IGT dev <igt-dev@lists.freedesktop.org>,
	Andi Shyti <andi@etezian.org>,
	Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [RFC PATCH v8 3/5] lib/igt_gt: use for_each_engine2 to loop through engines
Date: Wed, 13 Feb 2019 13:07:16 +0200	[thread overview]
Message-ID: <20190213110716.GB2104@intel.intel> (raw)
In-Reply-To: <155004960810.11832.6151477497817552511@skylake-alporthouse-com>

Hi Chris,

> > > > +#define for_each_engine2(fd, ctx, e) \
> > > > +               for (__set_ctx_engine_map(fd, ctx_id), \
> > > > +                    e = intel_active_engines2; e->name; e++) \
> > > > +                       for_if (gem_has_get_set_param() || \
> > > > +                               gem_has_engine(fd, e->class, e->instance))
> > > 
> > > intel_active_engines2 can define e->flags, and then you can just use
> > > gem_has_ring(fd, e->flags) for both ctx->engines[] and legacy.
> > 
> > Sorry, I haven't understood: 'e' is 'intel_execution_engine2' and
> > doesn't have flags. Indeed I call it as:
> 
> Then fix it.

If we want to add flags in 'intel_execution_engine2' (I tried to
minimize the amount of changes outside of my part), then the
whole thing can come out nicer and I guess could get rid of the
'gem_class_instance_to_eb_flags()' function.

But I think this is a bit off-topic from this patch series and I
can add it in my to-do list (which would this way have already
two items) for the next days.

Andi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-02-13 11:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 23:54 [igt-dev] [RFC PATCH v8 0/5] new engine discovery interface Andi Shyti via igt-dev
2019-02-12 23:54 ` [igt-dev] [RFC PATCH v8 1/5] include/drm-uapi: import i915_drm.h header file Andi Shyti via igt-dev
2019-02-12 23:54 ` [igt-dev] [RFC PATCH v8 2/5] lib/i915: add gem_query library Andi Shyti via igt-dev
2019-02-13  0:13   ` Chris Wilson
2019-02-13  0:55     ` Andi Shyti via igt-dev
2019-02-13  9:19       ` Chris Wilson
2019-02-13  9:55         ` Andi Shyti via igt-dev
2019-02-13 10:00           ` Chris Wilson
2019-02-12 23:54 ` [igt-dev] [RFC PATCH v8 3/5] lib/igt_gt: use for_each_engine2 to loop through engines Andi Shyti via igt-dev
2019-02-13  0:16   ` Chris Wilson
2019-02-13  1:19     ` Andi Shyti via igt-dev
2019-02-13  9:20       ` Chris Wilson
2019-02-13 11:07         ` Andi Shyti via igt-dev [this message]
2019-02-12 23:54 ` [igt-dev] [RFC PATCH v8 4/5] lib: ioctl_wrappers: reach engines by index as well Andi Shyti via igt-dev
2019-02-13  0:19   ` Chris Wilson
2019-02-13  1:11     ` Andi Shyti via igt-dev
2019-02-13  9:22       ` Chris Wilson
2019-02-12 23:54 ` [igt-dev] [RFC PATCH v8 5/5] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test Andi Shyti via igt-dev
2019-02-13  0:23   ` Chris Wilson
2019-02-13  1:02     ` Andi Shyti via igt-dev
2019-02-13  0:28 ` [igt-dev] ✓ Fi.CI.BAT: success for new engine discovery interface Patchwork
2019-02-13  2:44 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20190213110716.GB2104@intel.intel \
    --to=igt-dev@lists.freedesktop.org \
    --cc=andi.shyti@intel.com \
    --cc=andi@etezian.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=petri.latvala@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 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.