Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1254547 > unrolled thread

[for-next][PATCH 0/2] tracing: More updates for 4.4

Started bySteven Rostedt <rostedt@goodmis.org>
First post2015-10-23 14:40 +0200
Last post2015-10-23 14:40 +0200
Articles 3 — 1 participant

Back to article view | Back to linux.kernel


Contents

  [for-next][PATCH 0/2] tracing: More updates for 4.4 Steven Rostedt <rostedt@goodmis.org> - 2015-10-23 14:40 +0200
    [for-next][PATCH 2/2] ftrace: Calculate the correct dyn_ftrace number to report to the  userspace Steven Rostedt <rostedt@goodmis.org> - 2015-10-23 14:40 +0200
    [for-next][PATCH 1/2] tracing: Remove {start,stop}_branch_trace Steven Rostedt <rostedt@goodmis.org> - 2015-10-23 14:40 +0200

#1254547 — [for-next][PATCH 0/2] tracing: More updates for 4.4

FromSteven Rostedt <rostedt@goodmis.org>
Date2015-10-23 14:40 +0200
Subject[for-next][PATCH 0/2] tracing: More updates for 4.4
Message-ID<qmJNx-1va-33@gated-at.bofh.it>
  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: 883a1e867e0fe7c2dc2e5844ef692f80177631d5


Dmitry Safonov (1):
      tracing: Remove {start,stop}_branch_trace

Minfei Huang (1):
      ftrace: Calculate the correct dyn_ftrace number to report to the userspace

----
 arch/x86/kernel/ftrace.c    |  4 ++++
 kernel/trace/trace_branch.c | 15 ++-------------
 2 files changed, 6 insertions(+), 13 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1254555 — [for-next][PATCH 2/2] ftrace: Calculate the correct dyn_ftrace number to report to the userspace

FromSteven Rostedt <rostedt@goodmis.org>
Date2015-10-23 14:40 +0200
Subject[for-next][PATCH 2/2] ftrace: Calculate the correct dyn_ftrace number to report to the userspace
Message-ID<qmJNx-1va-39@gated-at.bofh.it>
In reply to#1254547
From: Minfei Huang <mnfhuang@gmail.com>

Now, ftrace only calculate the dyn_ftrace number in the adding
breakpoint loop, not in adding update and finish update loop.

Calculate the correct dyn_ftrace, once ftrace reports the failure message
to the userspace.

Link: http://lkml.kernel.org/r/1442420382-13130-1-git-send-email-mnfhuang@gmail.com

Signed-off-by: Minfei Huang <mnfhuang@gmail.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
 arch/x86/kernel/ftrace.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/arch/x86/kernel/ftrace.c b/arch/x86/kernel/ftrace.c
index 8b7b0a51e742..311bcf338f07 100644
--- a/arch/x86/kernel/ftrace.c
+++ b/arch/x86/kernel/ftrace.c
@@ -556,6 +556,7 @@ void ftrace_replace_code(int enable)
 	run_sync();
 
 	report = "updating code";
+	count = 0;
 
 	for_ftrace_rec_iter(iter) {
 		rec = ftrace_rec_iter_record(iter);
@@ -563,11 +564,13 @@ void ftrace_replace_code(int enable)
 		ret = add_update(rec, enable);
 		if (ret)
 			goto remove_breakpoints;
+		count++;
 	}
 
 	run_sync();
 
 	report = "removing breakpoints";
+	count = 0;
 
 	for_ftrace_rec_iter(iter) {
 		rec = ftrace_rec_iter_record(iter);
@@ -575,6 +578,7 @@ void ftrace_replace_code(int enable)
 		ret = finish_update(rec, enable);
 		if (ret)
 			goto remove_breakpoints;
+		count++;
 	}
 
 	run_sync();
-- 
2.6.1


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1254558 — [for-next][PATCH 1/2] tracing: Remove {start,stop}_branch_trace

FromSteven Rostedt <rostedt@goodmis.org>
Date2015-10-23 14:40 +0200
Subject[for-next][PATCH 1/2] tracing: Remove {start,stop}_branch_trace
Message-ID<qmJNy-1va-57@gated-at.bofh.it>
In reply to#1254547
From: Dmitry Safonov <0x7f454c46@gmail.com>

Both start_branch_trace() and stop_branch_trace() are used in only one
location, and are both static. As they are small functions there is no
need to keep them separated out.

Link: http://lkml.kernel.org/r/1445000689-32596-1-git-send-email-0x7f454c46@gmail.com

Signed-off-by: Dmitry Safonov <0x7f454c46@gmail.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
 kernel/trace/trace_branch.c | 15 ++-------------
 1 file changed, 2 insertions(+), 13 deletions(-)

diff --git a/kernel/trace/trace_branch.c b/kernel/trace/trace_branch.c
index e2e12ad3186f..3a2a73716a5b 100644
--- a/kernel/trace/trace_branch.c
+++ b/kernel/trace/trace_branch.c
@@ -125,25 +125,14 @@ void disable_branch_tracing(void)
 	mutex_unlock(&branch_tracing_mutex);
 }
 
-static void start_branch_trace(struct trace_array *tr)
-{
-	enable_branch_tracing(tr);
-}
-
-static void stop_branch_trace(struct trace_array *tr)
-{
-	disable_branch_tracing();
-}
-
 static int branch_trace_init(struct trace_array *tr)
 {
-	start_branch_trace(tr);
-	return 0;
+	return enable_branch_tracing(tr);
 }
 
 static void branch_trace_reset(struct trace_array *tr)
 {
-	stop_branch_trace(tr);
+	disable_branch_tracing();
 }
 
 static enum print_line_t trace_branch_print(struct trace_iterator *iter,
-- 
2.6.1


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web