From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/selftests: Disable preemption while setting up fence-timers
Date: Thu, 14 Mar 2019 11:50:42 +0000 [thread overview]
Message-ID: <155256424194.4168.9395617965602463702@skylake-alporthouse-com> (raw)
In-Reply-To: <71f08352-390f-cfe1-712d-1dd8ebf3e59e@linux.intel.com>
Quoting Tvrtko Ursulin (2019-03-14 11:37:19)
>
> On 13/03/2019 20:59, Chris Wilson wrote:
> > The impossible happens and a future fence expired while we were still
> > initialising. The probable cause is that the test was preempted and we
> > lost our scheduler cpu slice. Disable preemption during this test to
> > rule out preemption as a source of timer disruption.
> >
> > References: https://bugs.freedesktop.org/show_bug.cgi?id=110039
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
[snip]
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Pushed, closed bug and hope it never happens again.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-03-14 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 20:59 [PATCH] drm/i915/selftests: Disable preemption while setting up fence-timers Chris Wilson
2019-03-14 2:22 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-03-14 8:38 ` ✓ Fi.CI.IGT: " Patchwork
2019-03-14 11:37 ` [PATCH] " Tvrtko Ursulin
2019-03-14 11:50 ` Chris Wilson [this message]
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=155256424194.4168.9395617965602463702@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.