From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 10/11] drm/i915: Check PIN_NONFAULT overlaps in evict_for_node
Date: Thu, 28 Sep 2017 13:40:21 +0300 [thread overview]
Message-ID: <1506595221.5415.6.camel@linux.intel.com> (raw)
In-Reply-To: <150632880394.25830.10530062396860797026@mail.alporthouse.com>
On Mon, 2017-09-25 at 09:40 +0100, Chris Wilson wrote:
> Quoting Chris Wilson (2017-09-19 13:43:41)
> > Quoting Chris Wilson (2017-09-11 09:41:34)
> > > If the caller says that he doesn't want to evict any other faulting
> > > vma, honour that flag. The logic was used in evict_something, but not
> > > the more specific evict_for_node, now being used as a preliminary probe
> > > since commit 606fec956c0e ("drm/i915: Prefer random replacement before
> > > eviction search").
> > >
> > > Fixes: 606fec956c0e ("drm/i915: Prefer random replacement before eviction search")
> > > Fixes: 821188778b9b ("drm/i915: Choose not to evict faultable objects from the GGTT")
> > > References: https://patchwork.freedesktop.org/patch/174781/
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> >
> > Any chance of getting review to this point?
>
> Any better suggestions for resolving the incompletes in CI? Is this good
> enough to land right now and then we can improve again with a happy CI?
Review provided for the CI/bxt relevant parts.
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:40 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
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 [this message]
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=1506595221.5415.6.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;
as well as URLs for NNTP newsgroup(s).