From: Ingo Molnar <mingo@elte.hu>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Paul Mundt <lethal@linux-sh.org>,
Karim Yaghmour <karim@opersys.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Jes Sorensen <jes@sgi.com>,
Andrew Morton <akpm@osdl.org>, Tom Zanussi <zanussi@us.ibm.com>,
Richard J Moore <richardj_moore@uk.ibm.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
Michel Dagenais <michel.dagenais@polymtl.ca>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Christoph Hellwig <hch@infradead.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
William Cohen <wcohen@redhat.com>,
"Martin J. Bligh" <mbligh@mbligh.org>
Subject: Re: tracepoint maintainance models
Date: Mon, 18 Sep 2006 01:41:53 +0200 [thread overview]
Message-ID: <20060917234152.GA20374@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0609171816390.6761@scrub.home>
* Roman Zippel <zippel@linux-m68k.org> wrote:
> And yet again, you offer no prove at all and just work from
> assumptions. You throw in some magic "_full set_" of marker and just
> assume any change in that will completely break static tracers. [...]
i'm not sure i understand what you are trying to say here. Are you
saying that if i replaced half of the static markups with function
attributes (which would still provide equivalent functionality for
dynamic tracers), or if i removed a few dozen static markups with
dynamic scripts (which change too would be transparent to users of
dynamic tracers), that in this case static tracers would /not/ break?
[if yes then that would be the most puzzling suggestion ever posed in
this thread]
> You completely ignore that it might be possible to create some rules
> and educate users that the amount of exported events can't be
> completely static.
no serious trace user would accept it if for example half of their
static tracepoints would go away, because for example they were made
dynamic (or they were made function attributes).
that's the plain meaning of what i said. Were we to accept static
tracers, we'd be stuck with the full set of static tracepoints for a
long time, because users of static tracers would not accept a
significant reduction in the number of tracepoints. (even if those
"reduced" tracepoints were in fact just moved over to dynamic probes)
Was it truly confusing to you what i said? (in words that i thought were
more than clear) Please let me know and i'll try to formulate more
verbosely and more clearly when replying to you. This must be some
fundamental communication issue between you and me.
Ingo
next prev parent reply other threads:[~2006-09-17 23:50 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 9:40 The emperor is naked: why *comprehensive* static markup belongs in mainline Karim Yaghmour
2006-09-17 11:21 ` Paul Mundt
2006-09-17 14:36 ` tracepoint maintainance models Ingo Molnar
2006-09-17 15:02 ` Roman Zippel
2006-09-17 15:09 ` Ingo Molnar
2006-09-17 17:18 ` Roman Zippel
2006-09-17 23:27 ` Ingo Molnar
2006-09-17 23:41 ` Ingo Molnar [this message]
2006-09-18 0:17 ` Roman Zippel
2006-09-18 9:01 ` Jes Sorensen
2006-09-17 20:37 ` Roman Zippel
2006-09-17 22:34 ` Ingo Molnar
2006-09-17 15:36 ` Mathieu Desnoyers
2006-09-18 0:07 ` Ingo Molnar
2006-09-18 1:12 ` Karim Yaghmour
2006-09-18 1:13 ` Ingo Molnar
2006-09-18 2:32 ` Karim Yaghmour
2006-09-18 2:57 ` Ingo Molnar
2006-09-18 3:54 ` Karim Yaghmour
2006-09-18 4:09 ` Ingo Molnar
2006-09-18 4:43 ` Karim Yaghmour
2006-09-18 2:43 ` Mathieu Desnoyers
2006-09-18 3:21 ` Ingo Molnar
2006-09-18 4:26 ` Mathieu Desnoyers
2006-09-18 5:08 ` Ingo Molnar
2006-09-18 12:25 ` Frank Ch. Eigler
2006-09-18 15:02 ` Ingo Molnar
2006-09-18 15:45 ` Mathieu Desnoyers
2006-09-18 15:48 ` Alan Cox
2006-09-18 15:22 ` Ingo Molnar
2006-09-18 16:19 ` Alan Cox
2006-09-18 16:15 ` Ingo Molnar
2006-09-18 17:02 ` Alan Cox
2006-09-18 16:15 ` Frank Ch. Eigler
2006-09-18 17:02 ` Alan Cox
2006-09-18 17:27 ` Frank Ch. Eigler
2006-09-18 18:04 ` Alan Cox
2006-09-18 17:54 ` Martin Bligh
2006-09-18 18:05 ` Frank Ch. Eigler
2006-09-18 19:10 ` Vara Prasad
2006-09-18 19:49 ` Alan Cox
2006-09-18 19:39 ` Frank Ch. Eigler
2006-09-18 20:28 ` Vara Prasad
2006-10-06 5:33 ` Steven Rostedt
2006-10-06 13:01 ` Frank Ch. Eigler
2006-10-06 14:23 ` Steven Rostedt
2006-10-06 23:17 ` Jeremy Fitzhardinge
2006-09-18 15:47 ` Frank Ch. Eigler
2006-09-18 15:42 ` Ingo Molnar
2006-09-18 16:30 ` MARKER mechanism, try 2 Mathieu Desnoyers
2006-09-18 16:28 ` Ingo Molnar
2006-09-18 17:47 ` Mathieu Desnoyers
2006-09-18 19:39 ` Alan Cox
2006-09-17 20:19 ` tracepoint maintainance models Nicholas Miell
2006-09-17 23:06 ` Ingo Molnar
2006-09-18 0:05 ` Roman Zippel
2006-09-18 1:52 ` Theodore Tso
2006-09-19 12:58 ` tracing - consensus building insteat of dogfights Christoph Hellwig
2006-09-19 13:25 ` Roman Zippel
2006-09-19 13:45 ` Karim Yaghmour
2006-09-19 14:25 ` Karim Yaghmour
2006-09-18 0:10 ` tracepoint maintainance models Nicholas Miell
2006-09-18 0:43 ` Roman Zippel
2006-09-18 0:56 ` Karim Yaghmour
2006-09-18 0:56 ` Ingo Molnar
2006-09-18 2:09 ` Karim Yaghmour
2006-09-18 3:30 ` Ingo Molnar
2006-09-18 3:52 ` Theodore Tso
2006-09-18 4:11 ` Ingo Molnar
2006-09-18 4:24 ` Karim Yaghmour
2006-09-18 4:32 ` Ingo Molnar
2006-09-18 5:03 ` LTTng and SystemTAP (Everyone who is scared to read this huge thread, skip to here) Mathieu Desnoyers
2006-09-18 15:11 ` Ingo Molnar
2006-09-23 15:50 ` Mathieu Desnoyers
2006-09-18 5:37 ` tracepoint maintainance models Karim Yaghmour
2006-09-18 20:12 ` Michel Dagenais
2006-09-18 4:14 ` Karim Yaghmour
2006-09-18 4:09 ` Ingo Molnar
2006-09-18 4:57 ` Karim Yaghmour
2006-09-18 1:03 ` The emperor is naked: why *comprehensive* static markup belongs in mainline Karim Yaghmour
2006-09-18 15:53 ` Jose R. Santos
2006-09-18 17:28 ` Karim Yaghmour
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=20060917234152.GA20374@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=fche@redhat.com \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jes@sgi.com \
--cc=karim@opersys.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@mbligh.org \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@redhat.com \
--cc=richardj_moore@uk.ibm.com \
--cc=tglx@linutronix.de \
--cc=wcohen@redhat.com \
--cc=zanussi@us.ibm.com \
--cc=zippel@linux-m68k.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