public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <hiramatu@sdl.hitachi.co.jp>
To: systemtap@sources.redhat.com, ananth@in.ibm.com, "Keshavamurthy,
	Anil S" <anil.s.keshavamurthy@intel.com>
Cc: sugita@sdl.hitachi.co.jp, Satoshi Oshima <soshima@redhat.com>,
	Hideo Aoki <haoki@redhat.com>
Subject: [Patch 0/4][Djprobe] Djprobe update for linux-2.6.14-rc5-mm1
Date: Thu, 27 Oct 2005 13:22:00 -0000	[thread overview]
Message-ID: <4360D47D.4010703@sdl.hitachi.co.jp> (raw)

Hi,

I developed new four patches of djprobe for linux-2.6.14-rc5-mm1.
I took advices described below about previous patches in these
patches.

New features:
- separate djprobe code from */kprobe.{c,h}
- use hash table to find the djprobe instance in specified area.
- use wait_event() to wait for safety check worker.
- move some members of djprobe structure to arguments of
  register_djprobe() function.
- support lockless kprobe implementation.

TODO:
- support architecture transparent interface.
   (Djprobe interface emulated by kprobes)
- kprobe interoperability (coexistance in same address)
- support other architectures

patch 1:    Introduce a instruction slot management structure to
            handle different size slots.
patch 2:    Djprobe core patch.
patch 3:    Djprobe i386 patch.

Also, I developed a testing patch of bulk registration interface.

patch 4:    Testing patch of bulk interface for review.

If they are good enough, I will post first 3 patches (except the
bulk patch) to LKML.

Best Regards,

-- 
Masami HIRAMATSU
2nd Research Dept.
Hitachi, Ltd., Systems Development Laboratory
E-mail: hiramatu@sdl.hitachi.co.jp

             reply	other threads:[~2005-10-27 13:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27 13:22 Masami Hiramatsu [this message]
2005-10-27 13:26 ` [Patch 1/4][Djprobe] " Masami Hiramatsu
2005-10-27 13:28 ` [Patch 2/4][Djprobe] " Masami Hiramatsu
2005-10-27 13:30 ` [Patch 3/4][Djprobe] " Masami Hiramatsu
2005-10-27 13:31 ` [Patch 4/4][Djprobe][testing] " Masami Hiramatsu

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=4360D47D.4010703@sdl.hitachi.co.jp \
    --to=hiramatu@sdl.hitachi.co.jp \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=haoki@redhat.com \
    --cc=soshima@redhat.com \
    --cc=sugita@sdl.hitachi.co.jp \
    --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).