public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "zhangwei(Jovi)" <jovi.zhangwei@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Subject: [PATCH 0/2 v6] tracing/uprobes: Support multibuffer and soft-mode disabling
Date: Thu, 4 Jul 2013 19:04:07 +0800	[thread overview]
Message-ID: <51D556A7.30302@huawei.com> (raw)

This is sixth version of uprobes-based dynamic events
multibuffer and soft-mode disabling support work.

v5 -> v6:
- change list_for_each_entry to list_for_each_entry_rcu in
  uprobe_trace_func and uretprobe_trace_func, found by Namhyung Kim.

v4-> v5 (suggested by Oleg and Masami):
- code simply in probe_event_enable
- use list_del to replace list_del_rcu in probe_event_enable
- don't remove is_trace_uprobe_enabled() checking in probe_event_disable
  (I will check this later to figure out is it safe to remove that checking)

v3 -> v4:
- use "bool enabled = is_trace_uprobe_enabled(tu);", suggested by Oleg.
- use list_add_tail_rcu instead of list_add_rcu, suggested by Masami.
- fix the error handling in probe_event_enable, found by Srikar.

v3:
- separate soft-mode disabling patch from multibuffer support patch.
- fix some comments
- coding style trivial change
- fix flags race in probe_event_disable

zhangwei(Jovi) (2):
  tracing/uprobes: Support ftrace_event_file base multibuffer
  tracing/uprobes: Support soft-mode disabling

 kernel/trace/trace_uprobe.c |  122 ++++++++++++++++++++++++++++++++++++-------
 1 file changed, 103 insertions(+), 19 deletions(-)

-- 
1.7.9.7



                 reply	other threads:[~2013-07-04 11:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51D556A7.30302@huawei.com \
    --to=jovi.zhangwei@huawei.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=oleg@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.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