From: Sandeepa Prabhu <sandeepa.prabhu@linaro.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: systemtap@sourceware.org, William Cohen <wcohen@redhat.com>,
Petr Machata <pmachata@redhat.com>,
Mark Wielaard <mjw@redhat.com>,
Deepak Saxena <dsaxena@linaro.org>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
"sandeepa.prabhu@linux.com" <sandeepa.prabhu@linux.com>
Subject: Re: arm64 kprobes patches
Date: Thu, 27 Feb 2014 04:56:00 -0000 [thread overview]
Message-ID: <CA+b37P3zOuQdp-M64sKpPvSbQX+12=5f-B34RkVyT0e9RVf4TA@mail.gmail.com> (raw)
In-Reply-To: <530E9F9F.1060703@hitachi.com>
On 27 February 2014 07:44, Masami Hiramatsu
<masami.hiramatsu.pt@hitachi.com> wrote:
> (2014/02/27 0:02), Sandeepa Prabhu wrote:
>> Hi all,
>>
>> We have uploaded arm64 kprobes latest changes on linaro git which
>> include some fixes for recursive kprobes. These are rebased on top of
>> 3.14-rc3. Kprobes support can be enabled by enabling
>> "General setup ---> [*] Kprobes" config option.
>>
>> Git location: git://git.linaro.org/people/sandeepa.prabhu/linux-aarch64.git
>> Branch: arm64_kprobes_3.14-rc3
>
> Great! Thank you for working on that!
>
>>
>> Please let us know if you are interested in pulling this branch for
>> systemtap test-suite verification, while we are trying to include
>> systemtap test-suite on our linaro open-embedded platforms.
>>
>> Also, please let us know if there are documentation on howto run full
>> test-suite for systemtap and various criteria kprobes should meet?
>
> One possible testing is putting kprobes on all functions in the
> kernel by using ftrace interface. (On x86, current kprobes still has
> some problems, and I solved, will send the series later)
OK we will try to verify this with arm64 ftrace patches (from linaro)
which are close to get accepted upstream.
Has your earlier patches (kprobes blacklist related) been queued-up
for upstream? Are you planning generic kprobes API changes ?
>
> You can put kprobes on all kernel functions
> ----
> #!/bin/sh
> TRACE_DIR=/sys/kernel/debug/tracing/
> grep -iw t /proc/kallsyms | tr -d . | awk 'BEGIN{i=0};{print("p:"$3"_"i, "0x"$1); i++}' | \
> while read l; do echo $l >> $TRACE_DIR/kprobe_events || echo "Failed($?): $l" ; done
> ----
> Note that this just register *disabled* kprobes on each function.
> To enable each one, you need to write "1" to $TRACE_DIR/events/kprobes/<EVENT>/enable.
> # I recommend you to enable one by one, there still be a performance problem.
>
> Thank you,
> --
> Masami HIRAMATSU
> IT Management Research Dept. Linux Technology Center
> Hitachi, Ltd., Yokohama Research Laboratory
> E-mail: masami.hiramatsu.pt@hitachi.com
>
>
next prev parent reply other threads:[~2014-02-27 4:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 15:03 Sandeepa Prabhu
2014-02-26 16:36 ` Frank Ch. Eigler
2014-02-27 4:42 ` Sandeepa Prabhu
2014-02-27 11:48 ` Frank Ch. Eigler
2014-02-27 2:15 ` Masami Hiramatsu
2014-02-27 4:56 ` Sandeepa Prabhu [this message]
2014-02-27 6:04 ` Masami Hiramatsu
2014-02-27 6:19 ` Sandeepa Prabhu
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='CA+b37P3zOuQdp-M64sKpPvSbQX+12=5f-B34RkVyT0e9RVf4TA@mail.gmail.com' \
--to=sandeepa.prabhu@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=dsaxena@linaro.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mjw@redhat.com \
--cc=pmachata@redhat.com \
--cc=sandeepa.prabhu@linux.com \
--cc=systemtap@sourceware.org \
--cc=wcohen@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).