From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jason Baron <jbaron@redhat.com>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: sched: trace: update trace_sched_wakeup()
Date: Tue, 16 Dec 2008 08:57:24 +0100 [thread overview]
Message-ID: <1229414244.14605.50.camel@twins> (raw)
In-Reply-To: <1229411223.14605.48.camel@twins>
On Tue, 2008-12-16 at 08:07 +0100, Peter Zijlstra wrote:
> Add the information needed to distinguish 'real' wakeups from 'false'
> wakeups.
I don't seem to be doing so well this morning...
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Thanks Dhaval!
> ---
> include/trace/sched.h | 4 ++--
> kernel/sched.c | 2 +-
> kernel/trace/trace_sched_switch.c | 2 +-
> kernel/trace/trace_sched_wakeup.c | 2 +-
> 4 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/include/trace/sched.h b/include/trace/sched.h
> index 9b2854a..a0861d2 100644
> --- a/include/trace/sched.h
> +++ b/include/trace/sched.h
> @@ -17,8 +17,8 @@ DECLARE_TRACE(sched_wait_task,
> TPARGS(rq, p));
>
> DECLARE_TRACE(sched_wakeup,
> - TPPROTO(struct rq *rq, struct task_struct *p),
> - TPARGS(rq, p));
> + TPPROTO(struct rq *rq, struct task_struct *p, int success),
> + TPARGS(rq, p, success));
>
> DECLARE_TRACE(sched_wakeup_new,
> TPPROTO(struct rq *rq, struct task_struct *p),
> diff --git a/kernel/sched.c b/kernel/sched.c
> index 0eff15b..953ded9 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -2329,7 +2329,7 @@ out_activate:
> success = 1;
>
> out_running:
> - trace_sched_wakeup(rq, p);
> + trace_sched_wakeup(rq, p, success);
> check_preempt_curr(rq, p, sync);
>
> p->state = TASK_RUNNING;
> diff --git a/kernel/trace/trace_sched_switch.c b/kernel/trace/trace_sched_switch.c
> index 8633905..d4db564 100644
> --- a/kernel/trace/trace_sched_switch.c
> +++ b/kernel/trace/trace_sched_switch.c
> @@ -49,7 +49,7 @@ probe_sched_switch(struct rq *__rq, struct task_struct *prev,
> }
>
> static void
> -probe_sched_wakeup(struct rq *__rq, struct task_struct *wakee)
> +probe_sched_wakeup(struct rq *__rq, struct task_struct *wakee, int success)
> {
> struct trace_array_cpu *data;
> unsigned long flags;
> diff --git a/kernel/trace/trace_sched_wakeup.c b/kernel/trace/trace_sched_wakeup.c
> index 0067b49..43586b6 100644
> --- a/kernel/trace/trace_sched_wakeup.c
> +++ b/kernel/trace/trace_sched_wakeup.c
> @@ -211,7 +211,7 @@ static void wakeup_reset(struct trace_array *tr)
> }
>
> static void
> -probe_wakeup(struct rq *rq, struct task_struct *p)
> +probe_wakeup(struct rq *rq, struct task_struct *p, int success)
> {
> int cpu = smp_processor_id();
> unsigned long flags;
>
> --
> 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/
next prev parent reply other threads:[~2008-12-16 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 7:07 sched: trace: update trace_sched_wakeup() Peter Zijlstra
2008-12-16 7:57 ` Peter Zijlstra [this message]
2008-12-16 11:06 ` Ingo Molnar
2008-12-16 15:47 ` Mathieu Desnoyers
2008-12-16 16:18 ` Peter Zijlstra
2008-12-16 17:01 ` Mathieu Desnoyers
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=1229414244.14605.50.camel@twins \
--to=peterz@infradead.org \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=srostedt@redhat.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