From: Christoph Hellwig <hch@infradead.org>
To: Prasanna S Panchamukhi <prasanna@in.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, suparna@in.ibm.com,
richardj_moore@uk.ibm.com
Subject: Re: [RFC] [PATCH 3/6] Kprobes: New interfaces for user-space probes
Date: Tue, 9 May 2006 10:36:14 +0100 [thread overview]
Message-ID: <20060509093614.GB26953@infradead.org> (raw)
In-Reply-To: <20060509070508.GC22493@in.ibm.com>
On Tue, May 09, 2006 at 12:35:08PM +0530, Prasanna S Panchamukhi wrote:
> This patch provides two interfaces to insert and remove
> user space probes. Each probe is uniquely identified by
> inode and offset within that executable/library file.
> Insertion of a probe involves getting the code page for
> a given offset, mapping it into the memory and then inserting
> the breakpoint at the given offset. Also the probe is added
> to the uprobe_table hash list. A uprobe_module data structure
> is allocated for every probed application/library image on disk.
> Removal of a probe involves getting the code page for a given
> offset, mapping that page into the memory and then replacing
> the breakpoint instruction with a the original opcode.
> This patch also provides aggregate probe handler feature,
> where user can define multiple handlers per probe.
This introduces interfaces that aren't used anywhere in the following
patches. That is completely not acceptable. Please provide a proper
userspace interface to this functionality, e.g. something based on the
RPN code from Richard's dprobes.
next prev parent reply other threads:[~2006-05-09 9:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 6:54 [RFC] [PATCH 0/6] Kprobes: User-space probes support for i386 Prasanna S Panchamukhi
2006-05-09 6:59 ` [RFC] [PATCH 1/6] Kprobes: Allow/deny exclusive write access to inodes Prasanna S Panchamukhi
2006-05-09 7:01 ` [RFC] [PATCH 2/6] Kprobes: Get one pagetable entry Prasanna S Panchamukhi
2006-05-09 7:05 ` [RFC] [PATCH 3/6] Kprobes: New interfaces for user-space probes Prasanna S Panchamukhi
2006-05-09 7:09 ` [RFC] [PATCH 4/6] Kprobes: Insert probes on non-memory resident pages Prasanna S Panchamukhi
2006-05-09 7:12 ` [RFC] [PATCH 5/6] Kprobes: Single step the original instruction out-of-line Prasanna S Panchamukhi
2006-05-09 7:15 ` [RFC] [PATCH 6/6] Kprobes: Remove breakpoints from the copied pages Prasanna S Panchamukhi
2006-05-09 17:04 ` Hugh Dickins
2006-05-10 12:17 ` Prasanna S Panchamukhi
2006-05-10 15:17 ` Hugh Dickins
2006-05-09 9:38 ` [RFC] [PATCH 5/6] Kprobes: Single step the original instruction out-of-line Christoph Hellwig
2006-05-10 0:47 ` bibo,mao
2006-05-10 14:19 ` Richard J Moore
2006-05-09 9:37 ` [RFC] [PATCH 4/6] Kprobes: Insert probes on non-memory resident pages Christoph Hellwig
2006-05-09 9:36 ` Christoph Hellwig [this message]
2006-05-09 15:11 ` [RFC] [PATCH 3/6] Kprobes: New interfaces for user-space probes Richard J Moore
2006-05-09 15:18 ` Christoph Hellwig
2006-05-09 17:41 ` Frank Ch. Eigler
2006-05-09 20:40 ` Adrian Bunk
2006-05-09 20:58 ` Frank Ch. Eigler
2006-05-09 22:35 ` Christoph Hellwig
2006-05-09 9:34 ` [RFC] [PATCH 2/6] Kprobes: Get one pagetable entry Christoph Hellwig
2006-05-09 15:34 [RFC] [PATCH 3/6] Kprobes: New interfaces for user-space probes Khushil Dep
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=20060509093614.GB26953@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
--cc=richardj_moore@uk.ibm.com \
--cc=suparna@in.ibm.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®