From: Chris Wilson <chris@chris-wilson.co.uk>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: tune down unknown unclaime write hsw debug message
Date: Tue, 08 Jan 2013 09:32:44 +0000 [thread overview]
Message-ID: <84c8a8$782k7i@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1357634037-32542-1-git-send-email-daniel.vetter@ffwll.ch>
On Tue, 8 Jan 2013 09:33:57 +0100, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> This could very well be caused by dirt left behind by the BIOS, so
> tune it down to the debug level.
If the issue is solely the one described, then it should be silence when
we takeover, just like all the other error/debug status registers.
DRM_DEBUG is a little too noisy for this, maybe we should look at
trace_print or one of the other dynamic debugs for this class of info?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-01-08 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 8:33 [PATCH] drm/i915: tune down unknown unclaime write hsw debug message Daniel Vetter
2013-01-08 9:32 ` Chris Wilson [this message]
2013-01-08 10:07 ` Daniel Vetter
2013-01-12 2:35 ` Ben Widawsky
2013-01-14 20:58 ` Paulo Zanoni
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='84c8a8$782k7i@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=daniel.vetter@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 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.