From: fche@redhat.com (Frank Ch. Eigler)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
linux-kernel@vger.kernel.org, Russell King <rmk@arm.linux.org.uk>,
systemtap@sources.redhat.com
Subject: Re: [PATCH] markers-linker-generic
Date: 11 Apr 2007 18:58:50 -0400 [thread overview]
Message-ID: <y0my7kyldqt.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <20070411110240.537ee25d.akpm@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> writes:
> [...] I am told that the systemtap developers plan to (or are)
> using this infrastructure.
Indeed.
> If correct: what is their reason for preferring it over kprobes?
> [...]
It's not a preference - it's more of a supplement. It's helpful when
some combination of such factors exists:
- kprobe int3-fault dispatching overhead orders of magnitude too high
- fault dispatching not permissible in some areas
- local context variables not easily retrievable via dwarf information
- dwarf information not available at all
- costs of permanently placed but passive marker acceptable
>From systemtap's point of view, instrumentation hooked to markers,
kprobes, and other facilities like timers, coexist just fine. A
greater number of probe-able event sources makes for a richer tool.
- FChE
prev parent reply other threads:[~2007-04-11 23:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 22:36 Mathieu Desnoyers
2007-04-10 22:48 ` [PATCH] markers-linker-m68knommu Mathieu Desnoyers
2007-04-10 22:49 ` [PATCH] markers-linker-mips Mathieu Desnoyers
2007-04-10 22:50 ` [PATCH] markers-linker-parisc Mathieu Desnoyers
2007-04-10 22:51 ` [PATCH] markers-linker-powerpc Mathieu Desnoyers
2007-04-10 22:52 ` [PATCH] markers-linker-ppc Mathieu Desnoyers
2007-04-10 22:53 ` [PATCH] markers-linker-s390 Mathieu Desnoyers
2007-04-10 22:54 ` [PATCH] markers-linker-sh Mathieu Desnoyers
2007-04-10 22:54 ` [PATCH] markers-linker-sh64 Mathieu Desnoyers
2007-04-10 22:55 ` [PATCH] markers-linker-sparc Mathieu Desnoyers
2007-04-10 22:56 ` [PATCH] markers-linker-sparc64 Mathieu Desnoyers
2007-04-10 22:57 ` [PATCH] markers-linker-um Mathieu Desnoyers
2007-04-10 22:58 ` [PATCH] markers-linker-v850 Mathieu Desnoyers
2007-04-10 22:58 ` [PATCH] markers-linker-x86_64 Mathieu Desnoyers
2007-04-10 22:59 ` [PATCH] markers-linker-xtensa Mathieu Desnoyers
2007-04-11 7:44 ` [PATCH] markers-linker-generic Russell King
2007-04-11 17:51 ` Mathieu Desnoyers
2007-04-11 18:02 ` Andrew Morton
2007-04-11 19:21 ` Mathieu Desnoyers
2007-04-11 21:45 ` Jim Keniston
2007-04-12 0:21 ` Vara Prasad
2007-04-11 20:41 ` Mathieu Desnoyers
2007-04-11 22:58 ` Frank Ch. Eigler [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=y0my7kyldqt.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=rmk@arm.linux.org.uk \
--cc=systemtap@sources.redhat.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
all inboxes | Powered by JetHome®