All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
	Jiri Olsa <jolsa@kernel.org>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: perf,tools: Remove usage of trace_sched_wakeup(.success)
Date: Tue, 13 May 2014 09:22:08 +0200	[thread overview]
Message-ID: <20140513072208.GB7980@gmail.com> (raw)
In-Reply-To: <20140512181946.GG13467@laptop.programming.kicks-ass.net>


* Peter Zijlstra <peterz@infradead.org> wrote:

> trace_sched_wakeup(.success) is a dead argument and has been for ages,

Always 0, or random value?

Thanks,

	Ingo

  parent reply	other threads:[~2014-05-13  7:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 18:19 perf,tools: Remove usage of trace_sched_wakeup(.success) Peter Zijlstra
2014-05-13  1:38 ` [PATCH] perf_tools/sched: Remove nr_state_machine_bugs in perf latency Dongsheng Yang
2014-05-13  1:42   ` Dongsheng Yang
2014-05-13 11:56     ` Jiri Olsa
2014-05-19 11:59   ` Jiri Olsa
2014-05-21  9:25     ` Peter Zijlstra
2014-05-21  5:54   ` [tip:perf/core] perf sched: " tip-bot for Dongsheng Yang
2014-05-13  7:22 ` Ingo Molnar [this message]
2014-05-13  6:34   ` perf,tools: Remove usage of trace_sched_wakeup(.success) Dongsheng Yang
2014-05-13 10:03     ` Peter Zijlstra
2014-05-13 10:10       ` Dongsheng Yang
2014-05-13 11:26         ` Peter Zijlstra
2014-05-13 17:14       ` Ingo Molnar
2014-05-13 17:30         ` Peter Zijlstra
2014-05-13 18:15           ` Peter Zijlstra
2014-05-13 10:00   ` Peter Zijlstra
2014-05-21  5:54 ` [tip:perf/core] perf tools: Remove usage of trace_sched_wakeup( .success) tip-bot for Peter Zijlstra

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=20140513072208.GB7980@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@infradead.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    /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.