From: "Frank Ch. Eigler" <fche@redhat.com>
To: Theodore Tso <tytso@mit.edu>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
systemtap@sourceware.org
Subject: Re: [RFC] simple dprobe like markers for the kernel
Date: Thu, 10 Jul 2008 18:20:00 -0000 [thread overview]
Message-ID: <20080710181822.GA20174@redhat.com> (raw)
In-Reply-To: <20080710153017.GB25939@mit.edu>
Hi -
On Thu, Jul 10, 2008 at 11:30:17AM -0400, Theodore Tso wrote:
> [...] When you said a tool could determine if the tracepoint had
> gotten optimized away, or the variables were no longer present, I
> assume you meant at compile time, right? So with the right tool
> built into the kbuild infrastructure, if we could simply print
> warnings when tracepoints had gotten optimized away [...]
It will be interesting to see how frequently such a warning appears
for a good suite of such mini markers, on a diversity of architectures
and compilers. Such data can help pronounce judgement on this approach.
> P.S. When you said that the current kernel markers are "a bit
> heavyweight", how bad are they in practice? Hundreds of cycles? More?
Good question. The only performance measurements I have seen posted
indicate negligible effects.
- FChE
next prev parent reply other threads:[~2008-07-10 18:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1215638551.3444.39.camel__22002.9595810503$1215638656$gmane$org@localhost.localdomain>
2008-07-10 2:30 ` Frank Ch. Eigler
2008-07-10 13:51 ` James Bottomley
2008-07-10 14:23 ` Frank Ch. Eigler
2008-07-10 14:46 ` James Bottomley
2008-07-10 15:30 ` Theodore Tso
2008-07-10 15:57 ` James Bottomley
2008-07-10 18:20 ` Frank Ch. Eigler [this message]
2008-07-12 18:23 ` [PATCH] " James Bottomley
2008-07-12 20:05 ` [PATCH] systemtap: add parser for simple markers James Bottomley
2008-07-12 23:08 ` Frank Ch. Eigler
2008-07-14 16:28 ` [PATCH] simple dprobe like markers for the kernel Masami Hiramatsu
2008-07-14 22:03 ` James Bottomley
2008-07-09 21:23 [RFC] " James Bottomley
2008-07-10 3:40 ` Mathieu Desnoyers
2008-07-10 13:55 ` James Bottomley
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=20080710181822.GA20174@redhat.com \
--to=fche@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=systemtap@sourceware.org \
--cc=tytso@mit.edu \
/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).