From: fche@redhat•com (Frank Ch. Eigler)
To: Masami Hiramatsu <mhiramat@kernel•org>
Cc: Steven Rostedt <rostedt@goodmis•org>,
Ingo Molnar <mingo@redhat•com>,
Alban Crequy <alban.crequy@gmail•com>,
Alban Crequy <alban@kinvolk•io>,
Alexei Starovoitov <ast@kernel•org>,
Jonathan Corbet <corbet@lwn•net>,
Arnaldo Carvalho de Melo <acme@redhat•com>,
Omar Sandoval <osandov@fb•com>,
linux-doc@vger•kernel.org, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org, iago@kinvolk•io,
michael@kinvolk•io, Dorau Lukasz <lukasz.dorau@intel•com>,
systemtap@sourceware•org
Subject: Re: [RFC PATCH tip/master 0/3] kprobes: tracing: kretprobe_instance dynamic allocation
Date: Wed, 29 Mar 2017 09:27:35 -0400 [thread overview]
Message-ID: <y0ma884tdq0.fsf@fche.csb> (raw)
In-Reply-To: <149076484118.24574.7083269903420611708.stgit@devbox> (Masami Hiramatsu's message of "Wed, 29 Mar 2017 14:20:51 +0900")
mhiramat wrote:
> Here is a correction of patches to introduce kretprobe_instance
> dynamic allocation for avoiding kretprobe silently miss-hits.
> [...]
Thanks, this looks automatically useful also to systemtap users.
- FChE
prev parent reply other threads:[~2017-03-29 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 5:20 [RFC PATCH tip/master 0/3] kprobes: tracing: kretprobe_instance dynamic allocation Masami Hiramatsu
2017-03-29 5:22 ` [RFC PATCH tip/master 1/3] trace: kprobes: Show sum of probe/retprobe nmissed count Masami Hiramatsu
2017-03-31 9:45 ` Alban Crequy
2017-03-29 5:23 ` [RFC PATCH tip/master 2/3] kprobes: Allocate kretprobe instance if its free list is empty Masami Hiramatsu
2017-03-29 6:30 ` Ingo Molnar
2017-03-29 8:25 ` Masami Hiramatsu
2017-03-29 17:18 ` Josh Stone
2017-03-30 0:39 ` Masami Hiramatsu
2017-03-30 6:53 ` Ingo Molnar
2017-03-30 13:01 ` Masami Hiramatsu
2017-04-12 6:42 ` Ingo Molnar
2017-03-30 13:03 ` Alban Crequy
2017-03-29 5:24 ` [RFC PATCH tip/master 3/3] kprobes: Limit kretprobe maximum instances Masami Hiramatsu
2017-03-29 13:27 ` Frank Ch. Eigler [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=y0ma884tdq0.fsf@fche.csb \
--to=fche@redhat$(echo .)com \
--cc=acme@redhat$(echo .)com \
--cc=alban.crequy@gmail$(echo .)com \
--cc=alban@kinvolk$(echo .)io \
--cc=ast@kernel$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=iago@kinvolk$(echo .)io \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=lukasz.dorau@intel$(echo .)com \
--cc=mhiramat@kernel$(echo .)org \
--cc=michael@kinvolk$(echo .)io \
--cc=mingo@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=osandov@fb$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
--cc=systemtap@sourceware$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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