[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOZdJXXHGW1iceWgB47wSUhG_hYA48JWtOPRrVRnL-EvRCxhBA@mail.gmail.com>
Date: Mon, 6 Mar 2023 12:49:30 -0600
From: Timur Tabi <timur@...nel.org>
To: Jim Cromie <jim.cromie@...il.com>
Cc: jbaron@...mai.com, gregkh@...uxfoundation.org,
dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
intel-gvt-dev@...ts.freedesktop.org,
intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
daniel.vetter@...ll.ch, linux@...musvillemoes.dk,
seanpaul@...omium.org, joe@...ches.com
Subject: Re: [PATCH v6 32/57] nouveau: adapt NV_DEBUG, NV_ATOMIC to use DRM.debug
On Sun, Sep 4, 2022 at 4:48 PM Jim Cromie <jim.cromie@...il.com> wrote:
>
> These 2 macros used drm_debug_enabled() on DRM_UT_{DRIVER,ATOMIC}
> respectively, replace those with drm_dbg_##cat invocations.
>
> this results in new class'd prdbg callsites:
>
> :#> grep nouveau /proc/dynamic_debug/control | grep class | wc
> 116 1130 15584
> :#> grep nouveau /proc/dynamic_debug/control | grep class | grep DRIVER | wc
> 74 704 9709
> :#> grep nouveau /proc/dynamic_debug/control | grep class | grep ATOMIC | wc
> 31 307 4237
> :#> grep nouveau /proc/dynamic_debug/control | grep class | grep KMS | wc
> 11 119 1638
>
> the KMS entries are due to existing uses of drm_dbg_kms().
>
> Signed-off-by: Jim Cromie <jim.cromie@...il.com>
Has this patch set been forgotten? It was posted six months ago and
there's no sign that it was picked up.
The changes to drm_debug_enabled have impacted NV_DEBUG and NV_ATOMIC
and something needs to be fixed. I posted a simpler patch a few weeks
ago, but maybe Jim's is better.
Powered by blists - more mailing lists