[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55f88956-48ea-08e3-c353-babb08f3a786@gmail.com>
Date: Fri, 2 Oct 2020 18:39:12 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Scott Branden <scott.branden@...adcom.com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Desmond Yan <desmond.yan@...adcom.com>
Cc: Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com,
Olof Johansson <olof@...om.net>
Subject: Re: [PATCH v6 11/14] misc: bcm-vk: add BCM_VK_QSTATS
On 10/2/2020 2:23 PM, Scott Branden wrote:
> Add BCM_VK_QSTATS Kconfig option to allow for enabling debug VK
> queue statistics.
>
> These statistics keep track of max, abs_max, and average for the
> messages queues.
>
> Co-developed-by: Desmond Yan <desmond.yan@...adcom.com>
> Signed-off-by: Desmond Yan <desmond.yan@...adcom.com>
> Signed-off-by: Scott Branden <scott.branden@...adcom.com>
would not it make more sense to have those debug prints be trace printks
instead? Given what you explained in the previous patch version and the
desire to correlate with other system wide activity, that might make
more sense. Looking at the kernel's log for debugging performance or
utilization or just to get a glimpse of what is going on is not quite
suited past probe.
--
Florian
Powered by blists - more mailing lists