From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 4/4] drm/i915/gt: Remove timeslice suppression
Date: Thu, 7 Jan 2021 10:16:57 +0000 [thread overview]
Message-ID: <cf61d2c2-c0c0-5eca-94b5-33cbd8e4ab26@linux.intel.com> (raw)
In-Reply-To: <160994932055.14894.15675793524963876311@build.alporthouse.com>
On 06/01/2021 16:08, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2021-01-06 15:57:49)
[snip]
>>> @@ -1363,16 +1336,16 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
>>> __unwind_incomplete_requests(engine);
>>>
>>> last = NULL;
>>> - } else if (need_timeslice(engine, last) &&
>>> - timeslice_expired(execlists, last)) {
>>> + } else if (timeslice_expired(engine, last)) {
>>> ENGINE_TRACE(engine,
>>> - "expired last=%llx:%lld, prio=%d, hint=%d, yield?=%s\n",
>>> - last->fence.context,
>>> - last->fence.seqno,
>>> - last->sched.attr.priority,
>>> + "expired:%s last=%llx:%lld, prio=%d, hint=%d, yield?=%s\n",
>>> + yesno(timer_expired(&execlists->timer)),
>>> + last->fence.context, last->fence.seqno,
>>> + rq_prio(last),
>>> execlists->queue_priority_hint,
>>> yesno(timeslice_yield(execlists, last)));
>>>
>>> + cancel_timer(&execlists->timer);
>>
>> What is this cancel for?
>
> This branch is taken upon yielding the timeslice, but we may not submit
> a new pair of contexts, leaving the timer active (and marked as
> expired). Since the timer remains expired, we will continuously looped
> until a context switch, or some other preemption event.
Sorry I was looking at the cancel_timer in process_csb and ended up
replying at the wrong spot. The situation there seems to be removing the
single timeslice related call (set_timeslice) and adding a cancel_timer
which is also not obvious to me what it is about.
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:[~2021-01-07 10:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 12:39 [Intel-gfx] [PATCH 1/4] drm/i915/selftests: Break out of the lrc layout test after register mismatch Chris Wilson
2021-01-06 12:39 ` [Intel-gfx] [PATCH 2/4] drm/i915/selftests: Improve handling of iomem around stolen Chris Wilson
2021-01-06 15:12 ` Tvrtko Ursulin
2021-01-06 12:39 ` [Intel-gfx] [PATCH 3/4] drm/i915/gt: Restore ce->signal flush before releasing virtual engine Chris Wilson
2021-01-06 12:39 ` [Intel-gfx] [PATCH 4/4] drm/i915/gt: Remove timeslice suppression Chris Wilson
2021-01-06 15:57 ` Tvrtko Ursulin
2021-01-06 16:08 ` Chris Wilson
2021-01-06 16:19 ` Chris Wilson
2021-01-07 10:16 ` Tvrtko Ursulin [this message]
2021-01-07 10:27 ` Chris Wilson
2021-01-07 12:52 ` Tvrtko Ursulin
2021-01-06 13:01 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915/selftests: Break out of the lrc layout test after register mismatch Patchwork
2021-01-06 13:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-01-06 13:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-06 15:10 ` [Intel-gfx] [PATCH 1/4] " Tvrtko Ursulin
2021-01-06 15:17 ` Chris Wilson
2021-01-06 15:28 ` Tvrtko Ursulin
2021-01-06 16:38 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/4] " 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=cf61d2c2-c0c0-5eca-94b5-33cbd8e4ab26@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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