From: Daniel Vetter <daniel@ffwll.ch>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2 4/5] drm/i915: Add a partial GGTT view type
Date: Thu, 7 May 2015 18:15:50 +0200 [thread overview]
Message-ID: <20150507161550.GF30184@phenom.ffwll.local> (raw)
In-Reply-To: <1430912448.9311.12.camel@jlahtine-mobl1>
On Wed, May 06, 2015 at 02:40:48PM +0300, Joonas Lahtinen wrote:
> On ke, 2015-05-06 at 12:20 +0200, Daniel Vetter wrote:
> > On Thu, Apr 30, 2015 at 01:16:30PM +0100, Tvrtko Ursulin wrote:
> > > On 04/30/2015 12:20 PM, Joonas Lahtinen wrote:
> > > >@@ -495,7 +503,10 @@ i915_ggtt_view_equal(const struct i915_ggtt_view *a,
> > > > if (WARN_ON(!a || !b))
> > > > return false;
> > > >
> > > >- return a->type == b->type;
> > > >+ if (a->type != b->type)
> > > >+ return false;
> > > >+
> > > >+ return !memcmp(&a->params, &b->params, sizeof(a->params));
> > >
> > > Still don't like this, would this be so bad:
> > >
> > > if (a->type != PARTIAL)
> > > return a->type == b->type;
> > > else
> > > return !memcmp(...)
> >
> > Why do we even need this? memcmp implies comparing just one part of the
> > struct, doesn't it? Of course this means we need to clear it, but imo
> > that's the rtdt anyway.
>
> I only noticed this comment now (just sent v3 of the series out), I'm
> fine with leaving it like it was in the revision 1, which means that the
> last line is return !memcmp(..), so if the patch is otherwise OK, shall
> I make a one more revision, or will you merge manually?
Already pulled in, please do a follow-up patch.
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-05-07 16:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1430392239.git.joonas.lahtinen@linux.intel.com>
2015-04-30 11:18 ` [PATCH v2 1/5] drm/i915: Do not clear mappings beyond VMA size Joonas Lahtinen
2015-04-30 11:19 ` [PATCH v2 2/5] drm/i915: Do not make assumptions on GGTT VMA sizes Joonas Lahtinen
2015-04-30 12:03 ` Tvrtko Ursulin
2015-05-06 11:43 ` Joonas Lahtinen
2015-04-30 11:20 ` [PATCH v2 3/5] drm/i915: Consider object pinned if any VMA is pinned Joonas Lahtinen
2015-04-30 11:20 ` [PATCH v2 4/5] drm/i915: Add a partial GGTT view type Joonas Lahtinen
2015-04-30 12:16 ` Tvrtko Ursulin
2015-05-06 10:20 ` Daniel Vetter
2015-05-06 11:40 ` Joonas Lahtinen
2015-05-07 16:15 ` Daniel Vetter [this message]
2015-04-30 11:21 ` [PATCH v2 5/5] drm/i915: Use partial view in mmap fault handler Joonas Lahtinen
2015-04-30 12:32 ` Tvrtko Ursulin
2015-04-30 14:54 ` Tvrtko Ursulin
2015-05-04 11:51 ` Joonas Lahtinen
2015-05-05 9:07 ` Tvrtko Ursulin
2015-05-06 11:30 ` Joonas Lahtinen
2015-05-01 20:56 ` shuang.he
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=20150507161550.GF30184@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.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