From: Roman Fietze <roman.fietze@telemotive.de>
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dynamic_debug: allow to set dynamic debug flags right at module load time
Date: Tue, 29 Jun 2010 13:25:29 +0200 [thread overview]
Message-ID: <201006291325.29983.roman.fietze@telemotive.de> (raw)
In-Reply-To: <20100528135549.GA2528@redhat.com>
Hello Jason, hello LKML,
On Friday 28 May 2010 15:55:49 Jason Baron wrote:
> right, i think we want to add something inside ddebug_add_module()
> that recognizes if the module was loaded with verbose=1. I think you
> can get at the parameters via module->kp, which we need to pass in
> as well.
Yes, I would first check if there's a section named "__verbose" as it
is right now. If yes, I would search the already setup module->kp for
the used parameter.
Proposals, not being sure how to implement that right now:
Default is to search e.g. for param "dprintk".
Provide a macro to override that default, e.g.
DPRINTK_PARAM("verbose")
If the default or defined bool or other integer parameter is unequal
to 0 enable the p-flag on module load for all debug statements of this
module.
Questions just in case the proposal is kind of ok:
Prepare the code to allow the setting of different future flags
unequal to 'p'?
Use a charp param instead of a bool to allow that?
Roman
--
Roman Fietze Telemotive AG Buero Muehlhausen
Breitwiesen 73347 Muehlhausen
Tel.: +49(0)7335/18493-45 http://www.telemotive.de
next prev parent reply other threads:[~2010-06-29 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 12:25 Roman Fietze
2010-05-26 18:35 ` Jason Baron
2010-05-27 5:05 ` Roman Fietze
2010-05-28 13:55 ` Jason Baron
2010-06-29 11:25 ` Roman Fietze [this message]
2010-07-01 20:43 ` Jason Baron
2010-07-02 8:16 ` [PATCH] dynamic_debug: parse module parameters to enable dynamic printk at " Roman Fietze
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=201006291325.29983.roman.fietze@telemotive.de \
--to=roman.fietze@telemotive.de \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®