From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 3/4] drm/i915: Mark all non-vma being inserted into the address spaces
Date: Fri, 18 Nov 2016 11:55:18 +0200 [thread overview]
Message-ID: <1479462918.3594.11.camel@linux.intel.com> (raw)
In-Reply-To: <20161118090531.GC16779@nuc-i3427.alporthouse.com>
On pe, 2016-11-18 at 09:05 +0000, Chris Wilson wrote:
> On Thu, Nov 17, 2016 at 02:12:19PM +0000, Chris Wilson wrote:
> > I've used i915_mm elsewhere as a subclass of struct mm, so a little wary
> > of I915_MM. The other users are enum i915_cache_level, but I didn't want
> > to imply that this is a cache level and I wanted something that could
> > clearly demarque the I-am-not-vma.
> >
> > Maybe COLOR_ME_PINNED?
>
> This morning I feel more like
> #define COLOR_UNEVICTABLE (-1)
I'd still slap at least I915_ in the front.
Regards, Joonas
> -Chris
>
--
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-18 9:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 12:08 [PATCH v2 1/4] drm: Define drm_mm_for_each_node_in_range() Chris Wilson
2016-11-17 12:08 ` [PATCH v2 2/4] drm: Check against color expansion in drm_mm_reserve_node() Chris Wilson
2016-11-17 13:20 ` Joonas Lahtinen
2016-11-17 12:08 ` [PATCH v2 3/4] drm/i915: Mark all non-vma being inserted into the address spaces Chris Wilson
2016-11-17 13:31 ` Joonas Lahtinen
2016-11-17 14:12 ` Chris Wilson
2016-11-18 9:05 ` Chris Wilson
2016-11-18 9:55 ` Joonas Lahtinen [this message]
2016-11-17 12:08 ` [PATCH v2 4/4] drm/i915: Fix i915_gem_evict_for_vma (soft-pinning) Chris Wilson
2016-11-18 9:18 ` Joonas Lahtinen
2016-11-18 10:14 ` Chris Wilson
2016-11-18 11:31 ` Joonas Lahtinen
2016-11-18 12:06 ` Chris Wilson
2016-11-18 12:14 ` Chris Wilson
2016-11-17 12:46 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/4] drm: Define drm_mm_for_each_node_in_range() Patchwork
2016-11-17 13:56 ` [PATCH v2 1/4] " Joonas Lahtinen
2016-11-17 14:49 ` [PATCH] " Chris Wilson
2016-11-18 8:43 ` Joonas Lahtinen
2016-11-17 16:53 ` ✗ Fi.CI.BAT: failure for series starting with drm: Define drm_mm_for_each_node_in_range() (rev2) 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=1479462918.3594.11.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 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.