From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Remove last traces of exec-id (GEM_BUSY)
Date: Tue, 05 Mar 2019 15:49:43 +0000 [thread overview]
Message-ID: <155180097865.27405.4374179294797702960@skylake-alporthouse-com> (raw)
In-Reply-To: <9ca9799e-1794-d39e-02a2-735bc4abec20@linux.intel.com>
Quoting Tvrtko Ursulin (2019-03-05 14:47:51)
>
> On 02/03/2019 10:06, Chris Wilson wrote:
> > As we allow per-context engine allows the legacy concept of
> > I915_EXEC_RING no longer applies universally. We are still exposing the
> > unrelated exec-id in GEM_BUSY, so transition this ioctl (once more
> > slightly changing its ABI, but no one cares) over to only reporting the
> > uabi-class (not instance as we can not foreseeably fit those into the
> > small bitmask).
> >
> > The only user of the extended ring information from GEM_BUSY is ddx/sna,
> > which tries to use the non-rcs business information to guide which
> > engine to use for subsequent operations on foreign bo. All that matters
> > for it is the decision between rcs and !rcs, so it is unaffected by the
> > change in higher bits.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
I need a corresponding ack on
https://patchwork.freedesktop.org/series/57457/
-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-05 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 10:06 Busy ABI bump Chris Wilson
2019-03-02 10:06 ` [PATCH 1/2] drm/i915: Store the BIT(engine->id) as the engine's mask Chris Wilson
2019-03-05 14:44 ` Tvrtko Ursulin
2019-03-05 14:59 ` Chris Wilson
2019-03-02 10:06 ` [PATCH 2/2] drm/i915: Remove last traces of exec-id (GEM_BUSY) Chris Wilson
2019-03-05 14:47 ` Tvrtko Ursulin
2019-03-05 15:49 ` Chris Wilson [this message]
2019-03-02 10:30 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915: Store the BIT(engine->id) as the engine's mask Patchwork
2019-03-02 10:31 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-03-02 11:01 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-02 15:41 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-03-02 15:44 ` 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=155180097865.27405.4374179294797702960@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.