All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Enable mmio_debug for vlv/chv
Date: Mon, 11 Jan 2016 18:53:10 +0200	[thread overview]
Message-ID: <87mvsckqh5.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20160108142049.GC652@nuc-i3427.alporthouse.com>

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

> On Fri, Jan 08, 2016 at 03:51:19PM +0200, Mika Kuoppala wrote:
>> With commit 8ac3e1bb76cc ("drm/i915: Add non claimed mmio checking
>> for vlv/chv") we now have chv/vlv support in place for detecting
>> unclaimed access. Also the perf hit of extra mmio read
>> is now only suffered if mmio_debug is set.
>> 
>> This allows us to stuff the macro for unclaimed reg
>> detection inside a generic gen6 register access, as now all
>> gens using these macros uses also unclaimed debugs, the one
>> exception being snb. We gain more clean and generic macros
>> and only downside is that snb will suffer one branch perf hit
>> without upside.
>> 
>> Note that the hsw write path debug register check now
>> happens before fifo check, but this should not make
>> any real difference.
>> 
>> As vlv/chv use the generic gen6 access macros, the consequence
>> is that they gain the mmio_debug feature.
>> 
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> I still fancy a GEN6_DBG_READ/WRITE_HEADER but with only a couple of
> gen, it doesn't seem worth the argument. (Though we still need to reduce
> the expense of ilk_irq_handler, but for the most part that is to avoid
> these vfunc altogether.)
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris

Both patches pushed to dinq. Thankyou for review.

-Mika
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-01-11 16:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 13:51 [PATCH 1/2] drm/i915: Enable mmio_debug for vlv/chv Mika Kuoppala
2016-01-08 13:51 ` [PATCH 2/2] drm/i915: Arm the unclaimed mmio debugs on suspend path Mika Kuoppala
2016-01-08 14:18   ` Chris Wilson
2016-01-08 14:20 ` [PATCH 1/2] drm/i915: Enable mmio_debug for vlv/chv Chris Wilson
2016-01-11 16:53   ` Mika Kuoppala [this message]
2016-01-11  9:59 ` ✗ failure: Fi.CI.BAT Patchwork
2016-01-11 12:50   ` Mika Kuoppala
2016-01-12 16:22     ` Daniel Vetter
2016-01-13  9:16       ` Mika Kuoppala
2016-01-13  9:20       ` Mika Kuoppala
2016-01-13  9:39         ` Daniel Vetter
2016-01-13  9:39           ` Daniel Vetter

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=87mvsckqh5.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@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.