[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230203150834.GA2751526@linux.intel.com>
Date: Fri, 3 Feb 2023 16:08:34 +0100
From: Stanislaw Gruszka <stanislaw.gruszka@...ux.intel.com>
To: Jani Nikula <jani.nikula@...el.com>
Cc: Jim Cromie <jim.cromie@...il.com>, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
intel-gvt-dev@...ts.freedesktop.org,
intel-gfx@...ts.freedesktop.org, daniel.vetter@...ll.ch,
seanpaul@...omium.org, Thomas Zimmermann <tzimmermann@...e.de>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v3 00/19] fix DRM_USE_DYNAMIC_DEBUG regression
On Fri, Feb 03, 2023 at 11:34:02AM +0200, Jani Nikula wrote:
> On Wed, 25 Jan 2023, Jim Cromie <jim.cromie@...il.com> wrote:
> > Hi everyone,
> >
> > In v6.1 DRM_USE_DYNAMIC_DEBUG=y has a regression enabling drm.debug in
> > drivers at modprobe.
>
> I realize we haven't actually addressed the regression in any way yet,
> and any distro enabling DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE will have
> DRM_USE_DYNAMIC_DEBUG=y by default, and we're hitting the issue with
> trying to gather logs from users on v6.1 or later. It hampers debugging
> pretty badly.
>
> I appreciate the effort in fixing the problem properly here, but we'll
> need a fix that we can backport to stable kernels.
>
> Maybe just Ville's idea of
>
> config DRM_USE_DYNAMIC_DEBUG
> bool "use dynamic debug to implement drm.debug"
> - default y
> + default n
> + depends on BROKEN
> depends on DRM
> depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE
>
> but we'll need that as a patch and merged and backported ASAP.
+1 for this
Regards
Stanislaw
Powered by blists - more mailing lists