From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Subject: Re: [PATCH v2 1/3] drm/i915: Drop racy markup of missed-irqs from idle-worker
Date: Thu, 21 Jul 2016 11:28:02 +0100 [thread overview]
Message-ID: <5790A3B2.1000303@linux.intel.com> (raw)
In-Reply-To: <20160721101050.GL10317@nuc-i3427.alporthouse.com>
On 21/07/16 11:10, Chris Wilson wrote:
> On Thu, Jul 21, 2016 at 10:58:05AM +0100, Tvrtko Ursulin wrote:
>>
>> On 21/07/16 07:57, Chris Wilson wrote:
>>> During the idle-worker we disable the hangcheck and so kick any waiters
>>> that should have been completed (since the GPU is now idle). Unlike the
>>> hangcheck, we do not take any care to avoid the race between the irq
>>> handler and ourselves, and so it is possible for us to declare a missed
>>> interrupt even as the bottom-half is being scheduled to run. Let's
>>> ignore this race to stop a potential false-positive error.
>>
>> If the bottom half is scheduled to run then then..
>>
>>> References: https://bugs.freedesktop.org/show_bug.cgi?id=96974
>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>>> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
>>> ---
>>> drivers/gpu/drm/i915/i915_gem.c | 7 +++----
>>> 1 file changed, 3 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
>>> index 40047eb48826..9e826585edb2 100644
>>> --- a/drivers/gpu/drm/i915/i915_gem.c
>>> +++ b/drivers/gpu/drm/i915/i915_gem.c
>>> @@ -2706,10 +2706,9 @@ i915_gem_idle_work_handler(struct work_struct *work)
>>> rearm_hangcheck = false;
>>>
>>> stuck_engines = intel_kick_waiters(dev_priv);
>>
>> ... this will not return a stucked engine since the there is a bh
>> task assigned all until the bh exits.
>
> It reports if it wakes up a waiter on any engine. If the bh is already
> running, we cannot know if it has missed the seqno update. If it isn't
> running yet, we cannot know if it is about to be run.
Oh I read the logic as completely opposite than what it is.
Since the idle worker runs 100ms after last retirement, that would mean
a really slow waiter or what?
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:[~2016-07-21 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 6:57 [PATCH v2 1/3] drm/i915: Drop racy markup of missed-irqs from idle-worker Chris Wilson
2016-07-21 6:57 ` [PATCH v2 2/3] drm/i915: Update the breadcrumb interrupt counter before enabling Chris Wilson
2016-07-21 6:57 ` [PATCH v2 3/3] drm/i915: Check for a stuck waiter before a missed interrupt Chris Wilson
2016-07-21 18:34 ` Chris Wilson
2016-07-22 7:57 ` Chris Wilson
2016-07-21 7:55 ` ✓ Ro.CI.BAT: success for series starting with [v2,1/3] drm/i915: Drop racy markup of missed-irqs from idle-worker Patchwork
2016-07-21 9:58 ` [PATCH v2 1/3] " Tvrtko Ursulin
2016-07-21 10:10 ` Chris Wilson
2016-07-21 10:28 ` Tvrtko Ursulin [this message]
2016-07-21 11:04 ` Chris Wilson
2016-07-22 10:10 ` Tvrtko Ursulin
2016-07-22 10:22 ` 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=5790A3B2.1000303@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@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