From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH 04/11] drm/i915: Try harder to finish the idle-worker
Date: Thu, 28 Sep 2017 13:16:12 +0300 [thread overview]
Message-ID: <1506593772.5415.2.camel@linux.intel.com> (raw)
In-Reply-To: <20170911084135.22903-5-chris@chris-wilson.co.uk>
On Mon, 2017-09-11 at 09:41 +0100, Chris Wilson wrote:
> If a worker requeues itself, it may switch to a different kworker pool,
> which flush_work() considers as complete. To be strict, we then need to
> keep flushing the work until it is no longer pending.
>
> References: https://bugs.freedesktop.org/show_bug.cgi?id=102456
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@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
next prev parent reply other threads:[~2017-09-28 10:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 8:41 Fixes for CI/bxt Chris Wilson
2017-09-11 8:41 ` [PATCH 01/11] drm/i915: Mark the userptr invalidate workqueue as WQ_MEM_RECLAIM Chris Wilson
2017-09-11 11:33 ` Michał Winiarski
2017-09-15 9:19 ` Chris Wilson
2017-09-11 8:41 ` [PATCH 02/11] drm/i915/fence: Avoid del_timer_sync() from inside a timer Chris Wilson
2017-09-19 9:24 ` Chris Wilson
2017-09-19 10:19 ` Tvrtko Ursulin
2017-09-19 12:15 ` Chris Wilson
2017-09-11 8:41 ` [PATCH 03/11] drm/i915: Include fence-hint for timeout warning Chris Wilson
2017-09-28 10:14 ` Joonas Lahtinen
2017-09-11 8:41 ` [PATCH 04/11] drm/i915: Try harder to finish the idle-worker Chris Wilson
2017-09-28 10:16 ` Joonas Lahtinen [this message]
2017-09-11 8:41 ` [PATCH 05/11] drm/i915: Keep the device awake whilst in the GTT domain Chris Wilson
2017-09-14 14:58 ` [PATCH v2] " Chris Wilson
2017-09-11 8:41 ` [PATCH 06/11] drm/i915: Pin fence for iomap Chris Wilson
2017-09-28 10:20 ` Joonas Lahtinen
2017-09-11 8:41 ` [PATCH 07/11] drm/i915: Consolidate get_fence with pin_fence Chris Wilson
2017-09-11 8:41 ` [PATCH 08/11] drm/i915: Emit pipelined fence changes Chris Wilson
2017-09-11 8:41 ` [PATCH 09/11] drm/i915: Track user GTT faulting per-vma Chris Wilson
2017-09-11 8:41 ` [PATCH 10/11] drm/i915: Check PIN_NONFAULT overlaps in evict_for_node Chris Wilson
2017-09-19 12:43 ` Chris Wilson
2017-09-25 8:40 ` Chris Wilson
2017-09-28 10:40 ` Joonas Lahtinen
2017-09-11 8:41 ` [PATCH 11/11] drm/i915: Try a minimal attempt to insert the whole object for relocations Chris Wilson
2017-09-11 9:16 ` ✗ Fi.CI.BAT: warning for series starting with [01/11] drm/i915: Mark the userptr invalidate workqueue as WQ_MEM_RECLAIM Patchwork
2017-09-11 13:16 ` ✓ Fi.CI.BAT: success " Patchwork
2017-09-11 16:02 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-09-14 15:30 ` ✓ Fi.CI.BAT: success for series starting with [01/11] drm/i915: Mark the userptr invalidate workqueue as WQ_MEM_RECLAIM (rev2) Patchwork
2017-09-14 19:39 ` ✗ Fi.CI.IGT: failure " 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=1506593772.5415.2.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@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).