From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Hyeoncheol Lee <hyc.lee@gmail.com>
Cc: rostedt@goodmis.org, fweisbec@gmail.com, mingo@redhat.com,
LKML <linux-kernel@vger.kernel.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
"yrl.pp-manager.tt@hitachi.com" <yrl.pp-manager.tt@hitachi.com>
Subject: Re: [PATCH] uprobes tracer: Add support for @ADDR, @stackN, dereference, bitfield arguments
Date: Fri, 16 Nov 2012 21:22:03 +0900 [thread overview]
Message-ID: <50A62FEB.1000002@hitachi.com> (raw)
In-Reply-To: <1352877222-23797-1-git-send-email-hyc.lee@gmail.com>
Hi Hyeoncheol,
Thank you for working on uprobe enhancement!
First of all, I've failed to apply this on the latest tip tree
because of conflict with below patch.
http://marc.info/?l=linux-kernel&m=134869014622386
(2012/11/14 16:13), Hyeoncheol Lee wrote:
> Add support for @ADDR, @stackN, dereference, bitfield arguments. Uprobes
> tracer supported only register argument. @SYMBOL, $retval, $stack are not
> supported. because a symbol address and whether function starts at a given
> address can't be known.
I see why the @SYMBOL is not supported, but I can't understand the
reason why $retval and $stack aren't supported. At least we can
support $stack, isn't it?
> Uprobes tracer and kprobes tracer have their own fetch type information
> tables and fetch type functions. But they share printing type functions
> and some fetch type functions for register, dereference, and bitfield.
> The common functions are defined in trace_probe.c.
By the way, for easy to review and debug, please separate this
into several patches. This seems to do (1) moving some interfaces
out from trace_probe.c, (2) add fetch_size/fetch members into
recursive fetch function data, (3) introduce userspace memory
fetching functions, and some cleanups.
So, could you split those parts? unless, it is hard to maintain
the source code.
Thank you,
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
prev parent reply other threads:[~2012-11-16 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 7:13 [PATCH] uprobes tracer: Add support for @ADDR, @stackN, dereference, bitfield arguments Hyeoncheol Lee
2012-11-16 12:22 ` Masami Hiramatsu [this message]
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=50A62FEB.1000002@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=fweisbec@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=yrl.pp-manager.tt@hitachi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.