dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915: Improve debug Kconfig texts a bit
Date: Tue, 6 Jul 2021 10:11:15 +0200	[thread overview]
Message-ID: <YOQQIyAlLbbC+hmd@phenom.ffwll.local> (raw)
In-Reply-To: <162548570352.15289.12980604779254635228@jlahtine-mobl.ger.corp.intel.com>

On Mon, Jul 05, 2021 at 02:48:23PM +0300, Joonas Lahtinen wrote:
> Quoting Daniel Vetter (2021-07-02 23:17:08)
> > We're not consistently recommending these for developers only.
> > 
> > I stumbled over this due to DRM_I915_LOW_LEVEL_TRACEPOINTS, which was
> > added in
> > 
> > commit 354d036fcf70654cff2e2cbdda54a835d219b9d2
> > Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > Date:   Tue Feb 21 11:01:42 2017 +0000
> > 
> >     drm/i915/tracepoints: Add request submit and execute tracepoints
> > 
> > to "alleviate the performance impact concerns."
> > 
> > Which is nonsense.
> 
> I think that was the original reason why the patch was developed and
> it got merged primarily for the latter reason. Unfortunately the patch
> commit messages don't always get rewritten.
> 
> > Tvrtko and Joonas pointed out on irc that the real (but undocumented
> > reason) was stable abi concerns for tracepoints, see
> > 
> > https://lwn.net/Articles/705270/
> > 
> > and the specific change that was blocked around tracepoints:
> > 
> > https://lwn.net/Articles/442113/
> > 
> > Anyway to make it a notch clearer why we have this Kconfig option
> > consistly add the "Recommended for driver developers only." to it and
> > all the other debug options we have.
> > 
> > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Matthew Brost <matthew.brost@intel.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> 
> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

Pushed to drm-intel-gt-next, thanks for taking a look.
-Daniel

> 
> Regards, Joonas
> 
> > ---
> >  drivers/gpu/drm/i915/Kconfig.debug | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/Kconfig.debug b/drivers/gpu/drm/i915/Kconfig.debug
> > index 2ca88072d30f..f27c0b5873f7 100644
> > --- a/drivers/gpu/drm/i915/Kconfig.debug
> > +++ b/drivers/gpu/drm/i915/Kconfig.debug
> > @@ -215,6 +215,8 @@ config DRM_I915_LOW_LEVEL_TRACEPOINTS
> >           This provides the ability to precisely monitor engine utilisation
> >           and also analyze the request dependency resolving timeline.
> >  
> > +         Recommended for driver developers only.
> > +
> >           If in doubt, say "N".
> >  
> >  config DRM_I915_DEBUG_VBLANK_EVADE
> > @@ -228,6 +230,8 @@ config DRM_I915_DEBUG_VBLANK_EVADE
> >           is exceeded, even if there isn't an actual risk of missing
> >           the vblank.
> >  
> > +         Recommended for driver developers only.
> > +
> >           If in doubt, say "N".
> >  
> >  config DRM_I915_DEBUG_RUNTIME_PM
> > @@ -240,4 +244,6 @@ config DRM_I915_DEBUG_RUNTIME_PM
> >           runtime PM functionality. This may introduce overhead during
> >           driver loading, suspend and resume operations.
> >  
> > +         Recommended for driver developers only.
> > +
> >           If in doubt, say "N"
> > -- 
> > 2.32.0.rc2
> > 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

      reply	other threads:[~2021-07-06  8:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 20:17 [PATCH] drm/i915: Improve debug Kconfig texts a bit Daniel Vetter
2021-07-05 11:48 ` Joonas Lahtinen
2021-07-06  8:11   ` 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=YOQQIyAlLbbC+hmd@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=matthew.brost@intel.com \
    --cc=tvrtko.ursulin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox