From: Pratyush Anand <panand@redhat.com>
To: systemtap@sourceware.org
Subject: Re: [PATCH -tip v11 0/7] kprobes: NOKPROBE_SYMBOL for modules, and scalbility efforts
Date: Thu, 16 Jul 2015 08:59:00 -0000 [thread overview]
Message-ID: <loom.20150716T105448-54@post.gmane.org> (raw)
In-Reply-To: <55A71A9D.10603@hitachi.com>
Masami Hiramatsu <masami.hiramatsu.pt <at> hitachi.com> writes:
>
> On 2015/07/09 20:40, Pratyush Anand wrote:
> > It seems a useful series and without these patches system becomes extremely
> > slow with large number of kprobes enabled.
>
> Yes, I should revise it for the latest kernel...
Thanks :-)
[...]
> BTW, have you ever tried to analyze hot spot by using perf?
>
Not yet, but I will try on my ARM64 platform and will share findings with you.
~Pratyush
prev parent reply other threads:[~2015-07-16 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 8:20 Masami Hiramatsu
2014-05-14 8:20 ` [PATCH -tip v11 1/7] kprobes: Support blacklist functions in module Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 4/7] kprobes/x86: Remove unneeded preempt_disable/enable in interrupt handlers Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 6/7] kprobes: Introduce kprobe cache to reduce cache misshits Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 3/7] kprobes/x86: Use kprobe_blacklist for .kprobes.text and .entry.text Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 2/7] kprobes: Use NOKPROBE_SYMBOL() in sample modules Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 5/7] kprobes: Enlarge hash table to 512 entries Masami Hiramatsu
2014-05-14 8:21 ` [PATCH -tip v11 7/7] ftrace: Introduce FTRACE_OPS_FL_SELF_FILTER for ftrace-kprobe Masami Hiramatsu
2015-07-09 11:50 ` [PATCH -tip v11 0/7] kprobes: NOKPROBE_SYMBOL for modules, and scalbility efforts Pratyush Anand
2015-07-16 2:44 ` Masami Hiramatsu
2015-07-16 8:59 ` Pratyush Anand [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=loom.20150716T105448-54@post.gmane.org \
--to=panand@redhat.com \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).