From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915: Tune done rc6 enabling output
Date: Mon, 4 Aug 2014 17:43:59 +0200 [thread overview]
Message-ID: <20140804154359.GC8727@phenom.ffwll.local> (raw)
In-Reply-To: <20140804153428.GA15200@nuc-i3427.alporthouse.com>
On Mon, Aug 04, 2014 at 04:34:28PM +0100, Chris Wilson wrote:
> On Mon, Aug 04, 2014 at 11:18:27AM +0200, Daniel Vetter wrote:
> > Power users spot this and then get adventurous and try to adjust
> > module driver options. Nothing good ever came out of that, so
> > hide it better.
> >
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > ---
> > drivers/gpu/drm/i915/intel_pm.c | 12 ++++++------
> > 1 file changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > index 338a80b6773e..4f879494e0c5 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > @@ -3425,10 +3425,10 @@ static void intel_print_rc6_info(struct drm_device *dev, u32 mode)
> > else
> > mode = 0;
> > }
> > - DRM_INFO("Enabling RC6 states: RC6 %s, RC6p %s, RC6pp %s\n",
> > - (mode & GEN6_RC_CTL_RC6_ENABLE) ? "on" : "off",
> > - (mode & GEN6_RC_CTL_RC6p_ENABLE) ? "on" : "off",
> > - (mode & GEN6_RC_CTL_RC6pp_ENABLE) ? "on" : "off");
> > + DRM_DEBUG_KMS("Enabling RC6 states: RC6 %s, RC6p %s, RC6pp %s\n",
> > + (mode & GEN6_RC_CTL_RC6_ENABLE) ? "on" : "off",
> > + (mode & GEN6_RC_CTL_RC6p_ENABLE) ? "on" : "off",
> > + (mode & GEN6_RC_CTL_RC6pp_ENABLE) ? "on" : "off");
> > }
>
> I disagree. This is a good informative message about the capabilities
> enabled for their GPU. If you want to make the statement that the user
> shouldn't touch the values, make that adjustment emit a WARNING and
> implement the kernel tainting you suggested. Also fixing [drm] to be
> more specific would be useful.
Well I'd agree if we'd generally report this, but we don't. This really is
the only feature where we tell the user in dmesg what we've done with it,
for a lot of other stuff (psr, fbc, rps ...) we just silently set stuff
up. rc6 really is the only thing and I don't see why it's special. Imo
users should use tools like powertop to assess the effectivenes or our pm
code anyway, not look at dmesg.
So this is orthogonal to the module param tainting which unfortunately
missed 3.17 since Jani (who took over) went on vacatino before completing
the revised patches.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-08-04 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 9:18 [PATCH 1/2] drm/i915: Tune done rc6 enabling output Daniel Vetter
2014-08-04 9:18 ` [PATCH 2/2] drm/i915: Tune down MCH_SSKPD values warning Daniel Vetter
2014-08-04 15:03 ` Ville Syrjälä
2014-08-04 15:10 ` Paulo Zanoni
2014-08-04 15:07 ` [PATCH 1/2] drm/i915: Tune done rc6 enabling output Paulo Zanoni
2014-08-04 15:34 ` Chris Wilson
2014-08-04 15:43 ` Daniel Vetter [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=20140804154359.GC8727@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox