From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Intel graphics driver community testing & development
<intel-gfx@lists.freedesktop.org>
Subject: [PATCH v2 4/4] drm/i915: Use WARN_RECUR for recurring warning messages
Date: Fri, 18 Dec 2015 13:08:18 +0200 [thread overview]
Message-ID: <1450436898-20408-5-git-send-email-joonas.lahtinen@linux.intel.com> (raw)
In-Reply-To: <1450436898-20408-1-git-send-email-joonas.lahtinen@linux.intel.com>
Avoid flooding end users kernel log with warnings and mark recurring
warnings as such. This is a case when multiple code paths trigger a
warning and only displaying it once masks multiple errors in CI but
displaying it each time would make end user system log overflow
easily.
v2:
- Rebase for new macro name
- Remove a hunk belonging to previous patch
Cc: Imre Deak <imre.deak@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
---
drivers/gpu/drm/i915/intel_drv.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
index d523ebb..baac83c 100644
--- a/drivers/gpu/drm/i915/intel_drv.h
+++ b/drivers/gpu/drm/i915/intel_drv.h
@@ -1434,7 +1434,7 @@ void intel_display_power_put(struct drm_i915_private *dev_priv,
static inline void
assert_rpm_device_not_suspended(struct drm_i915_private *dev_priv)
{
- WARN_ONCE(dev_priv->pm.suspended,
+ WARN_RECUR(dev_priv->pm.suspended,
"Device suspended during HW access\n");
}
@@ -1442,7 +1442,7 @@ static inline void
assert_rpm_wakelock_held(struct drm_i915_private *dev_priv)
{
assert_rpm_device_not_suspended(dev_priv);
- WARN_ONCE(!atomic_read(&dev_priv->pm.wakeref_count),
+ WARN_RECUR(!atomic_read(&dev_priv->pm.wakeref_count),
"RPM wakelock ref not held during HW access");
}
@@ -1459,7 +1459,7 @@ assert_rpm_atomic_begin(struct drm_i915_private *dev_priv)
static inline void
assert_rpm_atomic_end(struct drm_i915_private *dev_priv, int begin_seq)
{
- WARN_ONCE(atomic_read(&dev_priv->pm.atomic_seq) != begin_seq,
+ WARN_RECUR(atomic_read(&dev_priv->pm.atomic_seq) != begin_seq,
"HW access outside of RPM atomic section\n");
}
--
2.4.3
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-12-18 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 11:08 [PATCH v2 0/4] Optionally display recurring warning messages Joonas Lahtinen
2015-12-18 11:08 ` [PATCH v2 1/4] drm/i915: Decouple struct i915_params i915 into i915_params.h Joonas Lahtinen
2015-12-18 11:08 ` [PATCH v2 2/4] drm/i915: Reorder i915_params struct Joonas Lahtinen
2015-12-21 13:35 ` Daniel Vetter
2015-12-18 11:08 ` [PATCH v2 3/4] drm/i915: Add WARN_RECUR and i915.recur_warnings Joonas Lahtinen
2015-12-18 11:30 ` Chris Wilson
2015-12-18 11:08 ` Joonas Lahtinen [this message]
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=1450436898-20408-5-git-send-email-joonas.lahtinen@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--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.