From: Carsten Emde <C.Emde@osadl.org>
To: Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: trace/latency-hist: Consider new argument when probing the sched_switch tracer
Date: Tue, 5 Jan 2016 10:21:59 +0100 [thread overview]
Message-ID: <568B8B37.9070804@osadl.org> (raw)
Hi Thomas & Sebastian,
The sched_switch tracer has got a new argument. Fix the latency tracer
accordingly.
Thanks,
-Carsten.
Signed-off-by: Carsten Emde <C.Emde@osadl.org>
---
kernel/trace/latency_hist.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux-4.4.0-rc6-rt1/kernel/trace/latency_hist.c
===================================================================
--- linux-4.4.0-rc6-rt1.orig/kernel/trace/latency_hist.c
+++ linux-4.4.0-rc6-rt1/kernel/trace/latency_hist.c
@@ -117,7 +117,7 @@ static char *wakeup_latency_hist_dir_sha
static notrace void probe_wakeup_latency_hist_start(void *v,
struct task_struct *p);
static notrace void probe_wakeup_latency_hist_stop(void *v,
- struct task_struct *prev, struct task_struct *next);
+ bool preempt, struct task_struct *prev, struct task_struct *next);
static notrace void probe_sched_migrate_task(void *,
struct task_struct *task, int cpu);
static struct enable_data wakeup_latency_enabled_data = {
@@ -907,7 +907,7 @@ out:
}
static notrace void probe_wakeup_latency_hist_stop(void *v,
- struct task_struct *prev, struct task_struct *next)
+ bool preempt, struct task_struct *prev, struct task_struct *next)
{
unsigned long flags;
int cpu = task_cpu(next);
next reply other threads:[~2016-01-05 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 9:21 Carsten Emde [this message]
2016-01-13 15:45 ` trace/latency-hist: Consider new argument when probing the sched_switch tracer Sebastian Andrzej Siewior
2016-01-13 15:51 ` Steven Rostedt
2016-01-13 16:08 ` Sebastian Andrzej Siewior
2016-01-15 11:30 ` Carsten Emde
2016-01-15 14:05 ` Steven Rostedt
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=568B8B37.9070804@osadl.org \
--to=c.emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.