From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Summers, Stuart" <stuart.summers@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915: Re-add enable_rc6 modparam
Date: Tue, 14 May 2019 17:06:04 -0700 [thread overview]
Message-ID: <20190515000604.GC18687@intel.com> (raw)
In-Reply-To: <4387e52b0895d400d4e0f5c71e4c8e0a164add7c.camel@intel.com>
On Tue, May 14, 2019 at 06:32:01PM +0000, Summers, Stuart wrote:
> On Tue, 2019-05-14 at 17:53 +0100, Chris Wilson wrote:
> > Quoting Stuart Summers (2019-05-14 17:46:52)
> > > To allow easier debug of platforms which do not fully support
> > > power-saving render C-state 6, add back the module parameter
> > > to allow RC6 flows to be disabled. Instead of directly affecting
> > > the RC6 states via a bitmask as done previously, use this module
> > > parameter to clear the has_rc6 field for these platforms.
> >
> > If you know which platforms don't support rc6, don't enable rc6.
>
> I'd really prefer to have this parameter in place for debug purposes.
> It seems more useful to allow quick testing by reloading i915 than by
> requiring a rebuild.
>
> Of course, once debug is complete and the platform is known to either
> not support the feature or has some cripling bug around this, I agree,
> rc6 shouldn't be enabled on that platform and i915 should be updated.
Exactly. We need the flexibility for debug that.
unfortunately using debugfs doesn't look a solution.
One possibility that just came to my mind now is, what if we make
this only for platforms that are still protected by is_alpha_support=1
(soon becoming require_force_probe=1)
But this is just one side of the coin... when product is out there
and we want the user to debug the issue to see if it is a RC6 bug
we have no way to verify that. :/
Please let's add this back one way or another.
Thanks,
Rodrigo.
>
> Thanks,
> Stuart
>
> > -Chris
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-15 0:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 16:46 [PATCH 1/2] drm/i915: Re-add enable_rc6 modparam Stuart Summers
2019-05-14 16:46 ` [PATCH 2/2] drm/i915: Extend reset modparam to domain resets Stuart Summers
2019-05-14 16:54 ` Chris Wilson
2019-05-14 17:03 ` Summers, Stuart
2019-05-14 16:53 ` [PATCH 1/2] drm/i915: Re-add enable_rc6 modparam Chris Wilson
2019-05-14 18:32 ` Summers, Stuart
2019-05-15 0:06 ` Rodrigo Vivi [this message]
2019-05-15 5:43 ` Tvrtko Ursulin
2019-05-15 14:16 ` Summers, Stuart
2019-05-16 9:59 ` Jani Nikula
2019-05-16 14:10 ` Summers, Stuart
2019-05-16 15:42 ` Jani Nikula
2019-05-16 15:49 ` Summers, Stuart
2019-05-17 16:17 ` Rodrigo Vivi
2019-05-17 16:34 ` Ville Syrjälä
2019-05-17 16:44 ` Rodrigo Vivi
2019-05-17 17:02 ` Ville Syrjälä
2019-05-21 19:17 ` Summers, Stuart
2019-05-14 17:07 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] " Patchwork
2019-05-14 17:29 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-15 0:23 ` ✗ Fi.CI.IGT: failure " 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=20190515000604.GC18687@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stuart.summers@intel.com \
/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.