From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Bump timeout for wait_for_engines()
Date: Tue, 12 Dec 2017 15:39:13 +0200 [thread overview]
Message-ID: <1513085953.3809.12.camel@linux.intel.com> (raw)
In-Reply-To: <20171211194135.27095-1-chris@chris-wilson.co.uk>
On Mon, 2017-12-11 at 19:41 +0000, Chris Wilson wrote:
> Extract the timeout we use in i915_gem_idle_work_handler() and reuse it
> for wait_for_engines() in i915_gem_wait_for_idle(). It too has the same
> problem in sometimes having to wait for an extended period before the HW
> settles, so make use of the same timeout.
>
> References: 5427f207852d ("drm/i915: Bump wait-times for the final CS interrupt before parking")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-12-12 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 19:41 [PATCH 1/2] drm/i915: Bump timeout for wait_for_engines() Chris Wilson
2017-12-11 19:41 ` [PATCH 2/2] drm/i915: Dump the engine state before declaring wedged from wait_for_engines() Chris Wilson
2017-12-12 13:40 ` Joonas Lahtinen
2017-12-12 21:40 ` Chris Wilson
2017-12-12 5:21 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Bump timeout for wait_for_engines() Patchwork
2017-12-12 6:25 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-12-12 13:39 ` Joonas Lahtinen [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=1513085953.3809.12.camel@linux.intel.com \
--to=joonas.lahtinen@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