From: Chris Wilson <chris@chris-wilson.co.uk>
To: Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: [PATCH] drm/i915: Engine discovery query
Date: Thu, 14 Mar 2019 15:03:42 +0000 [thread overview]
Message-ID: <155257582190.4168.9029124691050737358@skylake-alporthouse-com> (raw)
In-Reply-To: <20190314144419.20731-1-tvrtko.ursulin@linux.intel.com>
Quoting Tvrtko Ursulin (2019-03-14 14:44:19)
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Engine discovery query allows userspace to enumerate engines, probe their
> configuration features, all without needing to maintain the internal PCI
> ID based database.
>
> A new query for the generic i915 query ioctl is added named
> DRM_I915_QUERY_ENGINE_INFO, together with accompanying structure
Would ENGINE_UABI_INFO be apt if I were to add my gubbins as
ENGINE_HW_INFO ?
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-14 15:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2019-03-14 15:32 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Engine discovery query (rev7) Patchwork
2019-03-14 15:49 ` [PATCH] drm/i915: Engine discovery query Chris Wilson
2019-03-14 15:55 ` ✓ Fi.CI.BAT: success for drm/i915: Engine discovery query (rev7) Patchwork
2019-03-14 15:57 ` [PATCH] drm/i915: Engine discovery query Chris Wilson
2019-03-14 23:52 ` ✗ Fi.CI.IGT: failure for drm/i915: Engine discovery query (rev7) Patchwork
-- strict thread matches above, loose matches on Subject: below --
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
2018-10-02 9:49 ` 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=155257582190.4168.9029124691050737358@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.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.