From: Peter Hurley <peter@hurleysoftware.com>
To: Muni Sekhar <munisekharrms@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: enable dynamic debug - doubt
Date: Wed, 18 Nov 2015 16:08:54 -0500 [thread overview]
Message-ID: <564CE8E6.8060903@hurleysoftware.com> (raw)
In-Reply-To: <CAHhAz+g_p9_RnsHtm5fODD29oTp-71cMR0Hk7yG3g+ARD9hEeQ@mail.gmail.com>
On 11/17/2015 07:40 AM, Muni Sekhar wrote:
> [ Please keep me in CC as I'm not subscribed to the list]
>
> Hello,
>
> The behaviour of dynamic debug prints are controlled via writing to a
> control file in the 'debugfs'
> filesystem(<debugfs>/dynamic_debug/control).
That's not the only method. You'll want to read
Documentation/dynamic-debug-howto.txt; specifically, "Debug Messages at
Module Initialization Time" for ways to enable dynamic debug messages at
module load time.
Regards,
Peter Hurley
> Here I would like to know what order should the echo(for eg: echo -n
> 'module sdhci +p' > /sys/kernel/debug/dynamic_debug/control) be
> applied in relation to the module load - before or after?
next prev parent reply other threads:[~2015-11-18 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 12:40 Muni Sekhar
2015-11-18 19:12 ` Andy Shevchenko
2015-11-18 21:08 ` Peter Hurley [this message]
2015-11-19 8:47 ` Muni Sekhar
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=564CE8E6.8060903@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=munisekharrms@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome