From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 6/8] drm/i915/gt: Use virtual_engine during execlists_dequeue
Date: Mon, 18 May 2020 11:57:42 +0100 [thread overview]
Message-ID: <158979946209.17769.4780392433008098425@build.alporthouse.com> (raw)
In-Reply-To: <6339737f-1f48-34f9-f075-74fc1c72f65f@linux.intel.com>
Quoting Tvrtko Ursulin (2020-05-18 11:51:40)
>
> On 18/05/2020 09:14, Chris Wilson wrote:
> > @@ -2125,9 +2128,10 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
> > * find itself trying to jump back into a context it has just
> > * completed and barf.
> > */
> > -
> > if ((last = *active)) {
> > - if (need_preempt(engine, last, rb)) {
> > + ve = first_virtual_engine(engine);
>
> If you left this outside the if..
>
> > @@ -2212,9 +2216,8 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
> > }
> > }
> >
> > - while (rb) { /* XXX virtual is always taking precedence */
> > - struct virtual_engine *ve =
> > - rb_entry(rb, typeof(*ve), nodes[engine->id].rb);
> > + /* XXX virtual is always taking precedence */
> > + while ((ve = first_virtual_engine(engine))) {
>
> ... then here you wouldn't have to do a re-lookup of the same node, right?
But since we loop inside here, we need to recheck either at the continue
or here.
So:
ve = first_virtual_engine();
...
if (ve) do {
} while (ve = first_virtual_engine());
is kind of what we want, so a
while (ve) {
next_virtual_engine:
ve = first_virtual_engine()
}
instead of continues?
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-05-18 10:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 8:14 [Intel-gfx] [PATCH 1/8] drm/i915: Move saturated workload detection back to the context Chris Wilson
2020-05-18 8:14 ` [Intel-gfx] [PATCH 2/8] drm/i915/selftests: Add tests for timeslicing virtual engines Chris Wilson
2020-05-18 10:12 ` Tvrtko Ursulin
2020-05-18 10:21 ` Chris Wilson
2020-05-18 8:14 ` [Intel-gfx] [PATCH 3/8] drm/i915/gt: Reuse the tasklet priority for virtual as their siblings Chris Wilson
2020-05-18 10:13 ` Tvrtko Ursulin
2020-05-18 8:14 ` [Intel-gfx] [PATCH 4/8] drm/i915/gt: Kick virtual siblings on timeslice out Chris Wilson
2020-05-18 10:29 ` Tvrtko Ursulin
2020-05-18 8:14 ` [Intel-gfx] [PATCH 5/8] drm/i915/gt: Incorporate the virtual engine into timeslicing Chris Wilson
2020-05-18 10:36 ` Tvrtko Ursulin
2020-05-18 10:38 ` Chris Wilson
2020-05-18 8:14 ` [Intel-gfx] [PATCH 6/8] drm/i915/gt: Use virtual_engine during execlists_dequeue Chris Wilson
2020-05-18 10:51 ` Tvrtko Ursulin
2020-05-18 10:57 ` Chris Wilson [this message]
2020-05-18 12:33 ` [Intel-gfx] [PATCH v2] " Chris Wilson
2020-05-18 13:01 ` Tvrtko Ursulin
2020-05-18 13:09 ` Chris Wilson
2020-05-18 8:14 ` [Intel-gfx] [PATCH 7/8] drm/i915/gt: Decouple inflight virtual engines Chris Wilson
2020-05-18 12:53 ` Tvrtko Ursulin
2020-05-18 13:00 ` Chris Wilson
2020-05-18 14:55 ` Tvrtko Ursulin
2020-05-18 15:40 ` Chris Wilson
2020-05-18 15:48 ` Chris Wilson
2020-05-18 8:14 ` [Intel-gfx] [PATCH 8/8] drm/i915/gt: Resubmit the virtual engine on schedule-out Chris Wilson
2020-05-18 9:53 ` [Intel-gfx] [PATCH 1/8] drm/i915: Move saturated workload detection back to the context Tvrtko Ursulin
2020-05-18 10:11 ` Chris Wilson
2020-05-18 11:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/8] " Patchwork
2020-05-18 11:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-05-18 12:17 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-05-18 15:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/8] drm/i915: Move saturated workload detection back to the context (rev2) Patchwork
2020-05-18 15:57 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-05-18 16:28 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-05-18 7:57 [Intel-gfx] [PATCH 1/8] drm/i915: Move saturated workload detection back to the context Chris Wilson
2020-05-18 7:57 ` [Intel-gfx] [PATCH 6/8] drm/i915/gt: Use virtual_engine during execlists_dequeue 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=158979946209.17769.4780392433008098425@build.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).