From: Masami Hiramatsu <mhiramat@redhat.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Takashi Nishiie <t-nishiie@np.css.fujitsu.com>,
"'Alexey Dobriyan'" <adobriyan@gmail.com>,
"'Peter Zijlstra'" <peterz@infradead.org>,
"'Steven Rostedt'" <rostedt@goodmis.org>,
"'Frank Ch. Eigler'" <fche@redhat.com>,
"'Ingo Molnar'" <mingo@elte.hu>,
"'LKML'" <linux-kernel@vger.kernel.org>,
"'systemtap-ml'" <systemtap@sources.redhat.com>,
"'Hideo AOKI'" <haoki@redhat.com>
Subject: Re: [RFC PATCH] Kernel Tracepoints
Date: Sun, 29 Jun 2008 18:46:00 -0000 [thread overview]
Message-ID: <48656D9A.8000602@redhat.com> (raw)
In-Reply-To: <20080627131442.GA13751@Krystal>
Mathieu Desnoyers wrote:
> * Masami Hiramatsu (mhiramat@redhat.com) wrote:
>> Hi Mathieu,
>>
>> Thank you for making this so soon!
>>
>
> Hi Masami,
>
> Thanks for the comments, I will rework the patch accordingly.
>
> Also, one thing I thought about yesterday which I dislike is that if we
> have two modules declaring the same tracepoint in different headers with
> different prototypes, each declaration will be valid but the
> registration will try to connect a probe expecting wrong parameters to
> the other tracepoint.
>
> It would be the case if someone does :
>
> drivers/somedrivera/mydriver1-trace.h
>
> DECLARE_TRACE(really_generic_name, TPPTOTO(void), TPARGS()));
>
>
> drivers/somedriverb/mydriver2-trace.h
>
> DECLARE_TRACE(really_generic_name, TPPTOTO(struct somestruct *s), TPARGS(s)));
>
> Do you think it's worth it to append the prototype string to the
> tracepoint name ? I think it should fix the problem.
Hmm, I think we'd better send a fix patch to them in that case.
(I hope we can find that kind of conflicts soon)
I think we can make an external tool which detect those conflicts.
Anyway, signature based checking idea is good to me. I think ":" is
better delimiter.
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2008-06-27 22:47 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 19:36 [RFC][Patch 2/2] markers: example of irq regular kernel markers Masami Hiramatsu
2008-06-20 22:16 ` Mathieu Desnoyers
2008-06-20 23:23 ` Masami Hiramatsu
2008-06-21 15:08 ` KOSAKI Motohiro
2008-06-21 18:04 ` Steven Rostedt
2008-06-21 19:41 ` Frank Ch. Eigler
2008-06-22 4:03 ` Steven Rostedt
2008-06-22 4:32 ` Peter Zijlstra
2008-06-22 17:12 ` Frank Ch. Eigler
2008-06-23 2:20 ` Masami Hiramatsu
2008-06-23 7:08 ` KOSAKI Motohiro
2008-06-22 18:03 ` Frank Ch. Eigler
2008-06-22 18:27 ` Masami Hiramatsu
2008-06-21 10:14 ` Peter Zijlstra
2008-06-23 3:06 ` [RFC] Tracepoint proposal Mathieu Desnoyers
2008-06-23 6:34 ` Alexey Dobriyan
2008-06-23 6:51 ` Mathieu Desnoyers
2008-06-24 7:15 ` Alexey Dobriyan
2008-06-24 11:39 ` Masami Hiramatsu
2008-06-24 13:23 ` Takashi Nishiie
2008-06-24 16:23 ` Frank Ch. Eigler
2008-06-24 19:43 ` Masami Hiramatsu
2008-06-25 1:08 ` KOSAKI Motohiro
2008-06-25 1:36 ` Masami Hiramatsu
2008-06-25 1:49 ` Mathieu Desnoyers
2008-06-26 16:20 ` [RFC PATCH] Tracepoint sched probes Mathieu Desnoyers
2008-06-26 17:01 ` [RFC PATCH] Kernel Tracepoints Mathieu Desnoyers
2008-06-27 13:21 ` Masami Hiramatsu
2008-06-27 15:00 ` Mathieu Desnoyers
2008-06-29 18:46 ` Masami Hiramatsu [this message]
2008-06-30 18:21 ` Mathieu Desnoyers
2008-06-27 15:07 ` Mathieu Desnoyers
2008-06-30 20:11 ` Masami Hiramatsu
2008-06-27 15:48 ` Mathieu Desnoyers
2008-06-28 0:05 ` Masami Hiramatsu
2008-06-30 17:14 ` Mathieu Desnoyers
2008-06-30 20:17 ` Masami Hiramatsu
2008-07-03 15:13 ` Mathieu Desnoyers
2008-07-03 18:53 ` Masami Hiramatsu
2008-06-27 16:11 ` [RFC PATCH] Kernel Tracepoints (update) Mathieu Desnoyers
2008-07-03 15:29 ` Masami Hiramatsu
2008-07-03 15:47 ` Mathieu Desnoyers
2008-07-03 18:19 ` Mathieu Desnoyers
2008-07-03 18:48 ` Masami Hiramatsu
2008-06-24 11:06 ` [RFC] Tracepoint proposal Masami Hiramatsu
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=48656D9A.8000602@redhat.com \
--to=mhiramat@redhat.com \
--cc=adobriyan@gmail.com \
--cc=fche@redhat.com \
--cc=haoki@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.com \
--cc=t-nishiie@np.css.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).