From: "Frank Ch. Eigler" <fche@redhat.com>
To: Richard J Moore <richardj_moore@uk.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: next steps
Date: Wed, 21 Sep 2005 20:56:00 -0000 [thread overview]
Message-ID: <20050921205610.GB3989@redhat.com> (raw)
In-Reply-To: <OFD8E5432B.4ECF3557-ON41257083.0055883B-41257083.00563A05@uk.ibm.com>
Hi -
> Frank, under improving kprobes I would add:
Thanks for the suggestions.
> 1) dprobes or a scalable mechanism for performance tracing [...]
Could you elaborate on what exactly "scalable ... tracing" refers to,
and how you believe we're short of this?
> 2) watchpoint probes if these aren't already there. [...]
This is already tracked by bug #1324. A prerequisite is a debug
register management API in the kernel.
> 3) add back the ability to place probes in a code location before
> the module is loaded. [...] We used to have this capability for
> kernel modules. It relied on patches in insmod. Clearly this is
> useful especially when wanting to capture initialization module
> problems.
Sounds useful, especially if it can be accomplished without much or
any patching of generic kernel or kernel-utils code. Might the
register_module_notifier() hook be sufficient for this? It's worth
creating a bugzilla item for this. Bug #1145 is a prerequisite.
> 4) Finally I'd request that we re-instate the SysRq function to
> disable all probes instantly. [...]
Please create a bugzilla item. __sysrq_put_key_op is probably
suitable, as long as a handler doesn't try to do much anything fancy.
Is it safe to instantly remove all kprobes at an arbitrary moment?
> Apart from 1) all of these are simple modification for which the
> code has all ready been written.
These are good, though was intending to list the *larger* missing
chunks: leaps of usefulness that would excite ordinary developers, not
just kernel hackers.
- FChE
next prev parent reply other threads:[~2005-09-21 20:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 15:50 Frank Ch. Eigler
2005-09-21 15:46 ` Richard J Moore
2005-09-21 20:56 ` Frank Ch. Eigler [this message]
2005-09-21 23:33 ` Richard J Moore
2005-09-29 13:00 ` Masami Hiramatsu
2005-09-21 21:24 ` Martin Hunt
2005-09-21 23:58 ` Frank Ch. Eigler
2005-09-26 15:12 ` Jose R. Santos
2005-09-26 15:36 ` Frank Ch. Eigler
2005-09-26 16:26 ` Jose R. Santos
2005-09-26 16:56 ` Frank Ch. Eigler
2005-09-26 21:34 ` Jose R. Santos
2005-09-26 22:13 ` Frank Ch. Eigler
2005-09-27 15:30 ` Jose R. Santos
2005-09-26 17:44 ` thoughts Mathieu Desnoyers
2005-09-26 18:19 ` thoughts [re LTT] Frank Ch. Eigler
2005-09-26 18:30 ` Mathieu Desnoyers
2005-09-26 19:45 ` Karim Yaghmour
2005-09-29 16:44 ` thoughts Jose R. Santos
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=20050921205610.GB3989@redhat.com \
--to=fche@redhat.com \
--cc=richardj_moore@uk.ibm.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).