mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wang Nan <wangnan0@huawei.com>
To: <acme@kernel.org>, <masami.hiramatsu.pt@hitachi.com>,
	<rostedt@goodmis.org>
Cc: <mingo@redhat.com>, <namhyung@kernel.org>, <pi3orama@163.com>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/4] perf probe, tracing/uprobes: Support probing at absolute address
Date: Wed, 26 Aug 2015 07:40:21 +0000	[thread overview]
Message-ID: <1440574825-221187-1-git-send-email-wangnan0@huawei.com> (raw)

The goal of these 4 patches is to allow perf probing at absolute address
for uprobes and kprobes. During the development several small problem in
'perf probe -l' is found and fixed.

Patch 1 has already acked by Masami Hiramatsu.

Patch 2 fixes a problem about zero address in perf side.

Patch 3 is the main patch of these 4. It allows following command:

 # perf probe /lib/x86_64-linux-gnu/libc-2.19.so 0xeb860

 Different from v1, no extra '+' is required.

Patch 4 is a kernel side patch which fixes a small problem in uprobe_event
that, if address is 0, uprobe_events reports '0x  (null)'. It is independent
from the other patches.

Wang Nan (4):
  perf probe: Prevent segfault when reading probe point with absolute
    address
  perf probe: Fix list result when address is zero
  perf probe: Support probing at absolute address
  tracing/uprobes: Do not print '0x  (null)' when offset is 0

 kernel/trace/trace_uprobe.c    |  17 +++-
 tools/perf/util/probe-event.c  | 210 +++++++++++++++++++++++++++++++++++++----
 tools/perf/util/probe-event.h  |   4 +
 tools/perf/util/probe-finder.c |  21 +----
 4 files changed, 216 insertions(+), 36 deletions(-)

-- 
1.8.3.4


             reply	other threads:[~2015-08-26  7:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26  7:40 Wang Nan [this message]
2015-08-26  7:40 ` [PATCH v2 1/4] perf probe: Prevent segfault when reading probe point with " Wang Nan
2015-08-26  7:40 ` [PATCH v2 2/4] perf probe: Fix list result when address is zero Wang Nan
2015-08-26  9:29   ` 平松雅巳 / HIRAMATU,MASAMI
2015-08-26  9:43     ` Wangnan (F)
2015-08-26 10:48       ` 平松雅巳 / HIRAMATU,MASAMI
2015-08-26  7:40 ` [PATCH v2 3/4] perf probe: Support probing at absolute address Wang Nan
2015-08-26  9:49   ` 平松雅巳 / HIRAMATU,MASAMI
2015-08-26  7:40 ` [PATCH v2 4/4] tracing/uprobes: Do not print '0x (null)' when offset is 0 Wang Nan
2015-08-26 10:00   ` 平松雅巳 / HIRAMATU,MASAMI
2015-08-26  9:12 ` [PATCH v2 0/4] perf probe, tracing/uprobes: Support probing at absolute address 平松雅巳 / HIRAMATU,MASAMI

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=1440574825-221187-1-git-send-email-wangnan0@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=pi3orama@163.com \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®