From: Joe Perches <joe@perches.com>
To: Frederic Weisbecker <fweisbec@gmail.com>,
Arjan van de Ven <arjan@infradead.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@elte.hu>, Sam Ravnborg <sam@ravnborg.org>,
Steven Rostedt <rostedt@goodmis.org>,
Zhaolei <zhaolei@cn.fujitsu.com>,
Tom Zanussi <tzanussi@gmail.com>, Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: RFC: introduce struct ksymbol
Date: Wed, 22 Apr 2009 18:31:46 -0700 [thread overview]
Message-ID: <1240450306.21848.187.camel@localhost> (raw)
In-Reply-To: <20090418160910.GA6212@nowhere>
On Sat, 2009-04-18 at 18:09 +0200, Frederic Weisbecker wrote:
> On Fri, Apr 17, 2009 at 12:55:33AM -0700, Joe Perches wrote:
> > On Wed, 2009-04-15 at 20:21 +0930, Rusty Russell wrote:
> > > The current symbol printing APIs are awful; we should address them first
> > > (like the %pF patch does) IMHO.
> > I suggest just %pS<type>
> > With %pS, struct ksym is probably not all that
> > useful unless it's for something like a sscanf.
> > Today there are these symbol uses:
> > name, offset, size, modname
> > So perhaps %pS<foo> where foo is any combination of:
> > n name
> > o offset
> > s size
> > m modname
> > a all
> > and if not specified is a name lookup ("%pSn").
> It seems to me a rather good idea, it offers a good granularity
> about what has to displayed.
After implementing this %pS<foo> in a local tree,
I started to remove all print_symbol uses.
print_symbol is used in <foo>_warning_symbol calls.
These <foo>_warning_symbol uses seem dead.
Are they in use in some way or should they just
be removed?
see: http://lkml.org/lkml/2009/2/5/142
$ grep -r --include=*.[chS] -nH -e warning_symbol *
arch/x86/kernel/dumpstack.c:115:print_trace_warning_symbol(void *data, char *msg, unsigned long symbol)
arch/x86/kernel/dumpstack.c:145: .warning_symbol = print_trace_warning_symbol,
arch/x86/kernel/stacktrace.c:17:save_stack_warning_symbol(void *data, char *msg, unsigned long symbol)
arch/x86/kernel/stacktrace.c:57: .warning_symbol = save_stack_warning_symbol,
arch/x86/kernel/stacktrace.c:64: .warning_symbol = save_stack_warning_symbol,
arch/x86/oprofile/backtrace.c:18:static void backtrace_warning_symbol(void *data, char *msg,
arch/x86/oprofile/backtrace.c:45: .warning_symbol = backtrace_warning_symbol,
arch/x86/include/asm/stacktrace.h:11: void (*warning_symbol)(void *data, char *msg, unsigned long symbol);
kernel/trace/trace_sysprof.c:64:backtrace_warning_symbol(void *data, char *msg, unsigned long symbol)
kernel/trace/trace_sysprof.c:93: .warning_symbol = backtrace_warning_symbol,
prev parent reply other threads:[~2009-04-23 1:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 0:00 [PATCH] vsprintf: introduce %pf Frederic Weisbecker
2009-04-15 0:09 ` Joe Perches
2009-04-15 0:13 ` Frederic Weisbecker
2009-04-15 1:57 ` Zhaolei
2009-04-15 15:26 ` Frederic Weisbecker
2009-04-15 2:17 ` Mike Frysinger
2009-04-15 2:38 ` Steven Rostedt
2009-04-15 3:13 ` KOSAKI Motohiro
2009-04-15 15:48 ` [PATCH v2] " Frederic Weisbecker
2009-04-18 17:51 ` Mike Frysinger
2009-04-29 19:09 ` [tip:core/printk] vsprintf: introduce %pf format specifier tip-bot for Frederic Weisbecker
2009-04-15 15:29 ` [PATCH] vsprintf: introduce %pf Frederic Weisbecker
2009-04-15 5:03 ` RFC: introduce struct ksymbol Joe Perches
2009-04-15 5:58 ` Ingo Molnar
2009-04-15 6:13 ` Pekka Enberg
2009-04-15 6:31 ` Ingo Molnar
2009-04-15 15:52 ` Frederic Weisbecker
2009-04-15 6:14 ` Joe Perches
2009-04-15 10:51 ` Rusty Russell
2009-04-17 7:55 ` Joe Perches
2009-04-18 16:09 ` Frederic Weisbecker
2009-04-19 2:05 ` Joe Perches
2009-04-23 1:31 ` Joe Perches [this message]
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=1240450306.21848.187.camel@localhost \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=tzanussi@gmail.com \
--cc=zhaolei@cn.fujitsu.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 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.