From: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>,
"rjw@sisk.pl" <rjw@sisk.pl>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linaro-dev@lists.linaro.org" <linaro-dev@lists.linaro.org>,
"patches@linaro.org" <patches@linaro.org>,
PDSW-power-team <PDSW-power-team@arm.com>
Subject: Re: [PATCH 1/2] cpufreq: Improve debug prints
Date: Wed, 17 Oct 2012 10:58:04 +0100 [thread overview]
Message-ID: <507E812C.2030507@arm.com> (raw)
In-Reply-To: <CAKohpom0Jk+DqAKXz_KWJhpdVAmmXWA2Tr97OpK6=Ke8+KrW8g@mail.gmail.com>
On 17/10/12 10:39, Viresh Kumar wrote:
> On 17 October 2012 14:55, Sudeep KarkadaNagesha
> <Sudeep.KarkadaNagesha@arm.com> wrote:
>> With CONFIG_DYNAMIC_DEBUG, you can control(enable/disable) debug
>> prints at different levels (file, module, line, function)
>
> Quickly went through this :)
> http://www.kernel.org/doc/ols/2009/ols2009-pages-39-46.pdf
>
May be kernel/Documentation/dynamic-debug-howto.txt is more up-to-date.
> My usecase is a bit different. I want to see all bootprints with
> cpufreq pr_debug
> prints. So, this prefixing will help there.
>
> Also, i am not sure if dynamic debug will help in boot prints too?
The document covers "Debug messages during Boot Process" even though I
have never tried :)
Regards,
Sudeep
next prev parent reply other threads:[~2012-10-17 9:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 5:20 [PATCH 1/2] cpufreq: Improve debug prints Viresh Kumar
[not found] ` <3b38cb8ab136e5af3a70fceb7d77ad9fc889eb3f.1350451100.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-10-17 5:20 ` [PATCH 2/2] cpufreq: Debugging options for the cpufreq subsystem Viresh Kumar
2012-10-17 5:20 ` Viresh Kumar
2012-10-17 9:20 ` Sudeep KarkadaNagesha
2012-10-17 5:39 ` [PATCH 1/2] cpufreq: Improve debug prints Joe Perches
2012-10-17 5:55 ` Viresh Kumar
2012-10-17 6:04 ` Joe Perches
2012-10-17 6:17 ` Viresh Kumar
2012-10-17 6:26 ` Joe Perches
2012-10-17 6:33 ` Viresh Kumar
2012-10-17 6:39 ` Joe Perches
[not found] ` <CAKohpo=fgz98F+1SBG9TgO0EsPd_XLznJ0Z__0ehsgm14EZK7A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-24 22:00 ` Rafael J. Wysocki
2012-10-24 22:00 ` Rafael J. Wysocki
2012-10-17 9:25 ` Sudeep KarkadaNagesha
2012-10-17 9:25 ` Sudeep KarkadaNagesha
2012-10-17 9:39 ` Viresh Kumar
2012-10-17 9:58 ` Sudeep KarkadaNagesha [this message]
2012-10-17 10:23 ` Viresh Kumar
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=507E812C.2030507@arm.com \
--to=sudeep.karkadanagesha@arm.com \
--cc=PDSW-power-team@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.