From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Don't spam dmesg with rps messages on vlv/chv
Date: Tue, 2 Sep 2014 16:17:34 +0300 [thread overview]
Message-ID: <20140902131734.GL4193@intel.com> (raw)
In-Reply-To: <20140902124529.GE25238@nuc-i3427.alporthouse.com>
On Tue, Sep 02, 2014 at 01:45:29PM +0100, Chris Wilson wrote:
> On Tue, Sep 02, 2014 at 03:12:17PM +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > If the GPU frequency isn't going to change don't spam dmesg with
> > debug messages about it.
>
> I'd be more worried about why. gen6_rps_idle()?
Hmm. Good question. I suppose the PMINTRMSK frobbing should prevent
it from doing that. rps_idle should not be involved since it tries to
set the max freq all the time when running some benchmark. I'll try
to investigate a bit more...
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-09-02 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 12:12 [PATCH] drm/i915: Don't spam dmesg with rps messages on vlv/chv ville.syrjala
2014-09-02 12:38 ` Jani Nikula
2014-09-29 14:54 ` Daniel Vetter
2014-09-02 12:45 ` Chris Wilson
2014-09-02 13:17 ` Ville Syrjälä [this message]
2014-09-02 13:46 ` Ville Syrjälä
2014-09-02 13:50 ` Chris Wilson
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=20140902131734.GL4193@intel.com \
--to=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox