public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Satoshi Oshima <soshima@redhat.com>
To: systemtap@sourceware.org
Cc: Vara Prasad <prasadav@us.ibm.com>,
	Jim Keniston <jkenisto@us.ibm.com>,
	        Hien Q Nguyen <nguyhien@us.ibm.com>,
	        Ananth N Mavinakayanahalli <mananth@in.ibm.com>,
	        "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>,
	        "Hideo AOKI@redhat" <haoki@redhat.com>,
	        sugita <sugita@sdl.hitachi.co.jp>,
	        Masami Hiramatsu <hiramatu@sdl.hitachi.co.jp>
Subject: TODOs of kprobe-booster
Date: Thu, 09 Mar 2006 16:02:00 -0000	[thread overview]
Message-ID: <44105158.1030707@redhat.com> (raw)

Hi all,

Kprobe-booster has survived in 2.6.16-rc5-mm3.
We want to prepare the next step.

I summarize TODOs of kprobe-booster.

multi probe booster:
Current kprobe-booster lose boostability when multiple
probes is put on the same address. Multi-probe-booster
solve this problem. First patch has already posted on
systemtap-ml and need to be reviewed. And also some
tweaks such as jprobe support is required.

multi byte instruction support on i386:
kprobe-booster should support multi byte instruction.
Current kprobe-booster only boosts single byte
instruction. Prefix or 2 byte instructions are
not supported.

support other architectures:
Currently, i386 architecture is only supported.
Porting to other architectures is needed. We have
started working on x86_64. And we also have a plan
to work on IA64.

But we have little experience of development on IA64.
And we don't have any hardware of other architectures.
We need your help such as some advice, review and
volunteer for porting to others such as ppc64 or sparc.


Thanks,
Satoshi

                 reply	other threads:[~2006-03-09 16:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=44105158.1030707@redhat.com \
    --to=soshima@redhat.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=haoki@redhat.com \
    --cc=hiramatu@sdl.hitachi.co.jp \
    --cc=jkenisto@us.ibm.com \
    --cc=mananth@in.ibm.com \
    --cc=nguyhien@us.ibm.com \
    --cc=prasadav@us.ibm.com \
    --cc=sugita@sdl.hitachi.co.jp \
    --cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).