From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tursulin@ursulin.net>
Subject: Re: [PATCH] drm/i915: Engine discovery query
Date: Tue, 2 Oct 2018 10:05:11 +0100 [thread overview]
Message-ID: <491d5363-4cb9-3ffb-9b4e-1b37042855a0@linux.intel.com> (raw)
In-Reply-To: <153842276099.23109.15570739404431618302@skylake-alporthouse-com>
On 01/10/2018 20:39, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-10-01 17:41:00)
>>
>> On 01/10/2018 17:24, Chris Wilson wrote:
>>> Quoting Tvrtko Ursulin (2018-10-01 17:15:24)
>>>> + len = sizeof(struct drm_i915_query_engine_info) +
>>>> + I915_NUM_ENGINES * sizeof(struct drm_i915_engine_info);
>>>
>>> Since I915_NUM_ENGINES is not ABI, and this will be using a 2-step
>>> query (1st to find length, 2nd to grab details), it should work with
>>> info->num_rings. If not, we have problems later ;)
>>
>> I don't follow, what do you plan to enumerate that would cause a problem?
>
> All I'm suggesting is to avoid any notion that this length is fixed
> indefinitely :)
You mean extra paranoid step of making sure reported len exactly matches
the number of reported engines * sizeof(engine_info)? uAPI is defined to
query required memory block size and then read the reported num_engines
so I think that's fine, but sure, I can make it match exactly.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-02 9:05 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 16:15 [PATCH] drm/i915: Engine discovery query Tvrtko Ursulin
2018-10-01 16:21 ` Tvrtko Ursulin
2018-10-01 16:23 ` Tvrtko Ursulin
2018-10-01 16:24 ` Chris Wilson
2018-10-01 16:41 ` Tvrtko Ursulin
2018-10-01 19:39 ` Chris Wilson
2018-10-02 9:05 ` Tvrtko Ursulin [this message]
2018-10-02 9:49 ` Chris Wilson
2018-10-01 16:40 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Engine discovery query (rev3) Patchwork
2018-10-01 17:02 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-01 18:59 ` ✓ Fi.CI.IGT: " Patchwork
2018-10-03 9:58 ` [PATCH v5] drm/i915: Engine discovery query Tvrtko Ursulin
2018-10-03 12:28 ` Chris Wilson
2018-10-03 12:42 ` Chris Wilson
2018-10-03 12:51 ` Tvrtko Ursulin
2018-10-03 12:56 ` Chris Wilson
2018-10-04 10:51 ` [PATCH v6] " Tvrtko Ursulin
2018-10-04 11:03 ` Lionel Landwerlin
2018-10-04 11:10 ` Lionel Landwerlin
2018-10-04 11:14 ` Tvrtko Ursulin
2018-10-04 11:32 ` [PATCH v7] " Tvrtko Ursulin
2018-10-04 11:38 ` Lionel Landwerlin
2018-10-04 14:32 ` Joonas Lahtinen
2018-10-05 8:34 ` Tvrtko Ursulin
2018-10-05 9:21 ` Chris Wilson
2018-10-05 11:09 ` Joonas Lahtinen
2018-10-04 16:33 ` [PATCH v6] " Chris Wilson
2018-10-05 8:26 ` Tvrtko Ursulin
2018-10-05 10:35 ` Chris Wilson
2018-10-03 10:09 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Engine discovery query (rev4) Patchwork
2018-10-03 10:30 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-10-04 11:53 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Engine discovery query (rev6) Patchwork
2018-10-04 12:14 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-04 19:05 ` ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-03-14 14:44 [PATCH] drm/i915: Engine discovery query Tvrtko Ursulin
2019-03-14 14:55 ` Chris Wilson
2019-03-14 15:03 ` Chris Wilson
2019-03-14 15:49 ` Chris Wilson
2019-03-14 15:57 ` Chris Wilson
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=491d5363-4cb9-3ffb-9b4e-1b37042855a0@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=tursulin@ursulin.net \
/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