All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Extract knowledge of register forcewake domains
Date: Thu, 7 Apr 2016 15:40:51 +0100	[thread overview]
Message-ID: <20160407144051.GG18061@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1460037940-14094-1-git-send-email-tvrtko.ursulin@linux.intel.com>

On Thu, Apr 07, 2016 at 03:05:38PM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> 
> Knowledge of which register per platform belonds in which
> forcewake domain was embedded in the MMIO accessors themselves.
> 
> Extract it into standalone macros so they can be used from
> new code in the following patches.
> 
> This causes GCC to compile some of the MMIO accessors slightly
> differently and grows the code a tiny amount. But none of the
> growth is on the fast-path so it does not matter hugely.
> 
> Affected sizes before:
> 
> 00000000000026f0 00000000000001a5 t gen6_read16
> 0000000000002390 00000000000001a5 t gen6_read32
> 00000000000028a0 00000000000001a5 t gen6_read64
> 
> 00000000000061d0 000000000000019e t gen8_write16
> 0000000000006510 000000000000019d t gen8_write32
> 0000000000006370 000000000000019d t gen8_write64
> 00000000000021f0 000000000000019d t gen8_write8
> 
> Affected sizes after:
> 
> 0000000000002840 00000000000001aa t gen6_read16
> 00000000000024e0 00000000000001a9 t gen6_read32
> 00000000000029f0 00000000000001a9 t gen6_read64
> 
> 0000000000004f20 00000000000001b5 t gen8_write16
> 0000000000004ba0 00000000000001b4 t gen8_write32
> 00000000000050e0 00000000000001b4 t gen8_write64
> 0000000000004d60 00000000000001b4 t gen8_write8
> 
> Other MMIO accessors are not affected in size.
> 
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Acked-by: Chris Wilson <chris@chris-wilson.co.uk>

Went through the macros side-by-side and confirmed it was supposed to
only be code motion. Silly compiler.

Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-04-07 14:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 14:05 [PATCH 1/3] drm/i915: Extract knowledge of register forcewake domains Tvrtko Ursulin
2016-04-07 14:05 ` [PATCH 2/3] drm/i915: Remove forcewake request registers from the shadowed table Tvrtko Ursulin
2016-04-07 14:41   ` Chris Wilson
2016-04-07 14:05 ` [PATCH 3/3] drm/i915: Only grab correct forcewake for the engine with execlists Tvrtko Ursulin
2016-04-07 14:24   ` Chris Wilson
2016-04-07 14:36     ` Tvrtko Ursulin
2016-04-07 14:59       ` Chris Wilson
2016-04-07 14:35   ` Chris Wilson
2016-04-07 14:52     ` Tvrtko Ursulin
2016-04-07 15:33       ` Chris Wilson
2016-04-07 15:56         ` [PATCH v3 " Tvrtko Ursulin
2016-04-12 13:18           ` Chris Wilson
2016-04-07 14:40 ` Chris Wilson [this message]
2016-04-07 16:32 ` ✗ Fi.CI.BAT: failure for series starting with [1/3] drm/i915: Extract knowledge of register forcewake domains 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=20160407144051.GG18061@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@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 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.