From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/5] drm/i915: Mark all non-vma being inserted into the address spaces
Date: Thu, 24 Nov 2016 13:34:04 +0200 [thread overview]
Message-ID: <1479987244.2911.2.camel@linux.intel.com> (raw)
In-Reply-To: <20161123141118.23876-3-chris@chris-wilson.co.uk>
On ke, 2016-11-23 at 14:11 +0000, Chris Wilson wrote:
> We need to distinguish between full i915_vma structs and simple
> drm_mm_nodes when considering eviction (i.e. we must be careful not to
> treat a mere drm_mm_node as a much larger i915_vma causing memory
> corruption, if we are lucky). To do this, color these not-a-vma with -1
> (I915_COLOR_UNEVICTABLE).
>
> v2...v200: New name for -1.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
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:[~2016-11-24 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 14:11 [PATCH 1/5] drm: Define drm_mm_for_each_node_in_range() Chris Wilson
2016-11-23 14:11 ` [PATCH 2/5] drm: Check against color expansion in drm_mm_reserve_node() Chris Wilson
2016-11-24 8:11 ` Daniel Vetter
2016-11-24 8:57 ` Daniel Vetter
2016-11-23 14:11 ` [PATCH 3/5] drm/i915: Mark all non-vma being inserted into the address spaces Chris Wilson
2016-11-24 11:34 ` Joonas Lahtinen [this message]
2016-11-23 14:11 ` [PATCH 4/5] drm/i915: Fix i915_gem_evict_for_vma (soft-pinning) Chris Wilson
2016-11-24 11:45 ` Joonas Lahtinen
2016-11-24 11:52 ` Chris Wilson
2016-11-23 14:11 ` [PATCH 5/5] drm/i915: Tidy i915_gem_valid_gtt_space() Chris Wilson
2016-11-24 11:49 ` Joonas Lahtinen
2016-11-23 16:15 ` ✗ Fi.CI.BAT: warning for series starting with [1/5] drm: Define drm_mm_for_each_node_in_range() 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=1479987244.2911.2.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