From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Douglas Niehaus <niehaus@eecs.ku.edu>,
Tom Zanussi <zanussi@us.ibm.com>,
Paul Mundt <lethal@linux-sh.org>, Jes Sorensen <jes@sgi.com>,
Richard J Moore <richardj_moore@uk.ibm.com>,
William Cohen <wcohen@redhat.com>,
"Martin J. Bligh" <mbligh@mbligh.org>,
Michel Dagenais <michel.dagenais@polymtl.ca>,
systemtap@sources.redhat.com, ltt-dev@shafik.org
Subject: Re: [PATCH] Linux Kernel Markers 0.2 for Linux 2.6.17
Date: Tue, 19 Sep 2006 15:45:15 -0400 [thread overview]
Message-ID: <20060919194515.GB18646@redhat.com> (raw)
In-Reply-To: <20060919193623.GA9459@Krystal>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
Hi -
On Tue, Sep 19, 2006 at 03:36:24PM -0400, Mathieu Desnoyers wrote:
> [...]
> > If you don't allow yourself to presume on-the-fly function
> > recompilation, then these markers would need to be made run-time
> > rather than compile-time configurable. That is, not like this:
> > [...]
> By making them run-time configurable, I don't see any whay not to bloat the
> kernel. How can be embed calls to printk+function+kprobe+djprobe without
> having some kind of performance impact ?
In order to have what we appear to need, we cannot avoid having some
impact. (Even NOPs have impact.)
Suppose that mbligh's clever but speculative idea has some nasty flaw,
once someone tried to reduce it to code. Do you see that markers
along the lines you've posted would be unsatisfactory? With that in
mind, is there point adding such markers now?
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-19 19:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 18:34 [PATCH] Linux Kernel Markers 0.2 for Linux 2.6.17 Mathieu Desnoyers
2006-09-19 8:39 ` S. P. Prasanna
2006-09-19 20:05 ` Mathieu Desnoyers
2006-09-19 18:51 ` Randy.Dunlap
2006-09-19 19:13 ` Mathieu Desnoyers
2006-09-19 19:23 ` Frank Ch. Eigler
2006-09-19 19:36 ` Mathieu Desnoyers
2006-09-19 19:45 ` Frank Ch. Eigler [this message]
2006-09-19 20:28 ` Mathieu Desnoyers
2006-09-19 21:07 ` Frank Ch. Eigler
2006-09-19 22:11 ` Karim Yaghmour
2006-09-20 13:20 ` Frank Ch. Eigler
2006-09-20 13:38 ` Mathieu Desnoyers
2006-09-20 14:57 ` Mathieu Desnoyers
2006-09-20 15:53 ` Frank Ch. Eigler
2006-09-20 16:37 ` Mathieu Desnoyers
2006-09-20 17:14 ` Mathieu Desnoyers
2006-09-20 13:46 ` Mathieu Desnoyers
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=20060919194515.GB18646@redhat.com \
--to=fche@redhat.com \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jes@sgi.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@mbligh.org \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@redhat.com \
--cc=niehaus@eecs.ku.edu \
--cc=richardj_moore@uk.ibm.com \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
--cc=wcohen@redhat.com \
--cc=zanussi@us.ibm.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