public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andi Shyti <andi.shyti@intel.com>
Cc: IGT dev <igt-dev@lists.freedesktop.org>, Andi Shyti <andi@etezian.org>
Subject: Re: [igt-dev] [RFC PATCH v10 4/6] lib: ioctl_wrappers: reach engines by index as well
Date: Thu, 7 Mar 2019 14:27:58 +0000	[thread overview]
Message-ID: <6fba9cb1-9155-1715-22ea-a44aa12cef6f@linux.intel.com> (raw)
In-Reply-To: <20190307135426.GD1418@intel.intel>


On 07/03/2019 13:54, Andi Shyti wrote:
> Hi Tvrtko,
> 
>>> With the new engine query method engines are reachable through
>>> an index and context they are combined with.
>>>
>>> The 'gem_has_ring()' becomes 'gem_context_has_engine()' that
>>> requires the index that the engine is mapped within the driver.
>>>
>>> The previous 'gem_has_ring()' function becomes a wrapper to the new
>>> 'gem_context_has_engine()'.
>>>
>>> Signed-off-by: Andi Shyti <andi.shyti@intel.com>
>>> ---
>>>    lib/ioctl_wrappers.c | 4 +++-
>>>    lib/ioctl_wrappers.h | 4 +++-
>>>    2 files changed, 6 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/lib/ioctl_wrappers.c b/lib/ioctl_wrappers.c
>>> index 39920f8707d2..a2597e282704 100644
>>> --- a/lib/ioctl_wrappers.c
>>> +++ b/lib/ioctl_wrappers.c
>>> @@ -1252,7 +1252,7 @@ void igt_require_gem(int fd)
>>>    	igt_require_f(err == 0, "Unresponsive i915/GEM device\n");
>>>    }
>>> -bool gem_has_ring(int fd, unsigned ring)
>>> +bool gem_context_has_engine(int fd, unsigned ring, unsigned ctx)
>>>    {
>>>    	struct drm_i915_gem_execbuffer2 execbuf;
>>>    	struct drm_i915_gem_exec_object2 exec;
>>> @@ -1268,6 +1268,8 @@ bool gem_has_ring(int fd, unsigned ring)
>>>    	execbuf.buffers_ptr = to_user_pointer(&exec);
>>>    	execbuf.buffer_count = 1;
>>>    	execbuf.flags = ring;
>>> +	execbuf.rsvd1 = ctx;
>>> +
>>>    	return __gem_execbuf(fd, &execbuf) == -ENOENT;
>>>    }
>>> diff --git a/lib/ioctl_wrappers.h b/lib/ioctl_wrappers.h
>>> index f0be26080da6..446e973b7449 100644
>>> --- a/lib/ioctl_wrappers.h
>>> +++ b/lib/ioctl_wrappers.h
>>> @@ -142,11 +142,13 @@ bool gem_has_exec_fence(int fd);
>>>    /* check functions which auto-skip tests by calling igt_skip() */
>>>    void gem_require_caching(int fd);
>>> -bool gem_has_ring(int fd, unsigned ring);
>>> +bool gem_context_has_engine(int fd, unsigned ring, unsigned ctx);
>>>    void gem_require_ring(int fd, unsigned ring);
>>>    bool gem_has_mocs_registers(int fd);
>>>    void gem_require_mocs_registers(int fd);
>>> +#define gem_has_ring(fd, ring) gem_context_has_engine(fd, ring, 0)
>>> +
>>>    /* prime */
>>>    struct local_dma_buf_sync {
>>>    	uint64_t flags;
>>>
>>
>> I don't understand why this. All current callers of gem_has_ring pass in eb
>> flags and not an index so how it can work?
> 
> This is because of patch 3/6 this makes the for_each_engine2()
> able to work with new and old api.

How does it do that? Maybe I am extra slow today..

How is the for_each_engine2 without a helper to get engine flags, or the 
index variable, supposed to be used if one wants to submit a batch to 
all engines:

for_each_engine2(...)
	eb(engine=??)

Both in legacy and engine discovery mode.

Regards,

Tvrtko

> Have I messed up the patch order?
> 
> Andi
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-03-07 14:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05 13:16 [igt-dev] [RFC PATCH v10 0/6] new engine discovery interface Andi Shyti
2019-03-05 13:16 ` [igt-dev] [RFC PATCH v10 1/6] include/drm-uapi: import i915_drm.h header file Andi Shyti
2019-03-05 13:16 ` [igt-dev] [RFC PATCH v10 2/6] lib/i915: add gem_engine_topology library Andi Shyti
2019-03-05 13:24   ` Chris Wilson
2019-03-07 13:00     ` Andi Shyti
2019-03-07 12:05   ` Tvrtko Ursulin
2019-03-07 13:42     ` Andi Shyti
2019-03-07 14:16       ` Tvrtko Ursulin
2019-03-07 14:59         ` Chris Wilson
2019-03-07 16:25           ` Tvrtko Ursulin
2019-03-05 13:16 ` [igt-dev] [RFC PATCH v10 3/6] lib/igt_gt: use for_each_engine2 to loop through engines Andi Shyti
2019-03-05 13:36   ` Chris Wilson
2019-03-07 12:07   ` Tvrtko Ursulin
2019-03-07 12:27     ` Tvrtko Ursulin
2019-03-07 13:52       ` Andi Shyti
2019-03-08  7:09   ` Tvrtko Ursulin
2019-03-05 13:16 ` [igt-dev] [RFC PATCH v10 4/6] lib: ioctl_wrappers: reach engines by index as well Andi Shyti
2019-03-05 13:27   ` Chris Wilson
2019-03-07 12:10   ` Tvrtko Ursulin
2019-03-07 13:54     ` Andi Shyti
2019-03-07 14:27       ` Tvrtko Ursulin [this message]
2019-03-07 15:46         ` Andi Shyti
2019-03-07 15:57           ` Andi Shyti
2019-03-07 16:28           ` Tvrtko Ursulin
2019-03-07 17:17             ` Andi Shyti
2019-03-08  6:59               ` Tvrtko Ursulin
2019-03-05 13:16 ` [igt-dev] [RFC PATCH v10 5/6] lib: move gem_context_has_engine from ioctl_wrappers to gem_context Andi Shyti
2019-03-05 13:16 ` [igt-dev] [RFC PATCH v10 6/6] tests: gem_exec_basic: add "exec-ctx" buffer execution demo test Andi Shyti
2019-03-05 14:13 ` [igt-dev] ✓ Fi.CI.BAT: success for new engine discovery interface Patchwork
2019-03-05 15:22 ` [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=6fba9cb1-9155-1715-22ea-a44aa12cef6f@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=andi.shyti@intel.com \
    --cc=andi@etezian.org \
    --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