From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: IGT dev <igt-dev@lists.freedesktop.org>, Andi Shyti <andi@etezian.org>
Subject: Re: [igt-dev] [PATCH v12 5/7] lib/i915: add gem_engine_topology library
Date: Tue, 19 Mar 2019 12:00:03 +0200 [thread overview]
Message-ID: <20190319100003.GA1135@intel.intel> (raw)
In-Reply-To: <155298860922.4168.17028662959715453239@skylake-alporthouse-com>
> > 1. gem_topology_has_engine(): checks if the engine is present by
> > querying the driver in a way that the caller function wouldn't
> > know if the above ioctls are implemented.
> >
> > 2. gem_set_eb_flags(): sets the execution buffer flag depending
> > whether it refers to context-engine mapping or not.
> >
> > 3. gem_context_execbuf(): is a wrapper that executes the buffer
> > in a way that the calling function doesn't know about the
> > ioctls in the driver.
>
> You are not going to get me to use gem_context_execbuf, or
> gem_set_eb_flags(). I just want a function that returns the flags for a
> given engine in this context, as 99% of the time I already expect to
> have the right flags.
That's fine, I thought it might be cleaner to have wrappers
around that abstracts whatever is below. But anyway that's an
easy fix just make a gem_get_eb_flags instead of a
gem_set_eb_flags.
The thing that I like less is that the chain of calls starts
getting too long and hard to follow.
On the other hand, the amount of thngs to be done before calling
an execbuf would starts being too demanding (therefore hard to
follow).
I think this check should be done directly by execbuf, so that
the caller function would be completely agnostic. But this
requires quite some re-work around, which definitely goes far
beyond the purpose of this patchset.
Andi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-19 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 23:28 [igt-dev] [PATCH v12 0/7] new engine discovery interface Andi Shyti
2019-03-18 23:28 ` [igt-dev] [PATCH v12 1/7] lib/igt_gt: remove unnecessary argument Andi Shyti
2019-03-18 23:28 ` [igt-dev] [PATCH v12 2/7] lib: ioctl_wrappers: reach engines by index as well Andi Shyti
2019-03-18 23:28 ` [igt-dev] [PATCH v12 3/7] lib: move gem_context_has_engine from ioctl_wrappers to gem_context Andi Shyti
2019-03-18 23:28 ` [igt-dev] [PATCH v12 4/7] include/drm-uapi: import i915_drm.h header file Andi Shyti
2019-03-18 23:28 ` [igt-dev] [PATCH v12 5/7] lib/i915: add gem_engine_topology library Andi Shyti
2019-03-19 9:43 ` Chris Wilson
2019-03-19 10:00 ` Andi Shyti [this message]
2019-03-19 10:18 ` Tvrtko Ursulin
2019-03-19 10:44 ` Andi Shyti
2019-03-19 11:01 ` Tvrtko Ursulin
2019-03-18 23:28 ` [igt-dev] [PATCH v12 6/7] lib/igt_gt: use for_each_engine_class_instance to loop through active engines Andi Shyti
2019-03-19 10:22 ` Tvrtko Ursulin
2019-03-19 10:26 ` Andi Shyti
2019-03-18 23:28 ` [igt-dev] [PATCH v12 7/7] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test Andi Shyti
2019-03-18 23:33 ` [igt-dev] ✗ Fi.CI.BAT: failure for new engine discovery interface 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=20190319100003.GA1135@intel.intel \
--to=andi.shyti@intel.com \
--cc=andi@etezian.org \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox