From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Limit the auto arming of mmio debugs on vlv/chv
Date: Thu, 21 Jan 2016 12:07:35 +0200 [thread overview]
Message-ID: <87bn8fjleg.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20160120104549.GC19130@phenom.ffwll.local>
Daniel Vetter <daniel@ffwll.ch> writes:
> On Wed, Jan 20, 2016 at 12:32:23PM +0200, Mika Kuoppala wrote:
>> The capability to detect unclaimed register access was
>> recently introduced for vlv/chv platforms. Apparently
>> there are plenty of unclaimed access on these platforms,
>> resulting in new dmesg warns. But as we are trying to form
>> a beachhead for CI/Bat, all new warns are adding to the
>> noise and thus not desirable at this point in time.
>>
>> Make it so that if in these platforms the automatic arming
>> was responsible for mmio_debug enabling, ignore the warns.
>>
>> If user/dev wants to fix these, he can still do so by
>> i915.mmio_debug=1234.
>>
>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> Yeah it sucks, but otoh this will make CI more useful for everyone else
> and we can keep the original test coverage even.
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Applied to dinq. Thanks for review.
-Mika
>
>> ---
>> drivers/gpu/drm/i915/intel_uncore.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
>> index c3c13dc929cb..bfa79e5c214e 100644
>> --- a/drivers/gpu/drm/i915/intel_uncore.c
>> +++ b/drivers/gpu/drm/i915/intel_uncore.c
>> @@ -631,6 +631,15 @@ __unclaimed_reg_debug(struct drm_i915_private *dev_priv,
>> const bool read,
>> const bool before)
>> {
>> + /* XXX. We limit the auto arming traces for mmio
>> + * debugs on these platforms. There are just too many
>> + * revealed by these and CI/Bat suffers from the noise.
>> + * Please fix and then re-enable the automatic traces.
>> + */
>> + if (i915.mmio_debug < 2 &&
>> + (IS_VALLEYVIEW(dev_priv) || IS_CHERRYVIEW(dev_priv)))
>> + return;
>> +
>> if (WARN(check_for_unclaimed_mmio(dev_priv),
>> "Unclaimed register detected %s %s register 0x%x\n",
>> before ? "before" : "after",
>> --
>> 2.5.0
>>
>
> --
> 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:[~2016-01-21 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 10:32 [PATCH] drm/i915: Limit the auto arming of mmio debugs on vlv/chv Mika Kuoppala
2016-01-20 10:45 ` Daniel Vetter
2016-01-21 10:07 ` Mika Kuoppala [this message]
2016-01-20 13:49 ` ✓ Fi.CI.BAT: success for " 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=87bn8fjleg.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--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