[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c239d5df-e069-2091-589e-30f341c2cbd3@infradead.org>
Date: Tue, 9 Jun 2020 09:03:39 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Matthew Wilcox <willy@...radead.org>,
Stanimir Varbanov <stanimir.varbanov@...aro.org>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-btrfs@...r.kernel.org, linux-acpi@...r.kernel.org,
netdev@...r.kernel.org, Joe Perches <joe@...ches.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jason Baron <jbaron@...mai.com>
Subject: Re: [PATCH v3 0/7] Venus dynamic debug
On 6/9/20 4:13 AM, Matthew Wilcox wrote:
> On Tue, Jun 09, 2020 at 01:45:57PM +0300, Stanimir Varbanov wrote:
>> Here is the third version of dynamic debug improvements in Venus
>> driver. As has been suggested on previous version by Joe [1] I've
>> made the relevant changes in dynamic debug core to handle leveling
>> as more generic way and not open-code/workaround it in the driver.
>>
>> About changes:
>> - added change in the dynamic_debug and in documentation
>> - added respective pr_debug_level and dev_dbg_level
>
> Honestly, this seems like you want to use tracepoints, not dynamic debug.
>
Also see this patch series:
https://lore.kernel.org/lkml/20200605162645.289174-1-jim.cromie@gmail.com/
[PATCH 00/16] dynamic_debug: cleanups, 2 features
It adds/expands dynamic debug flags quite a bit.
--
~Randy
Powered by blists - more mailing lists