From: Arun Sharma <asharma@fb.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Andrew Vagin <avagin@openvz.org>,
Oleg Strikov <OSTRIKOV@nvidia.com>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH 0/5] Teach perf tool to profile sleep times (V4)
Date: Mon, 4 Jun 2012 10:01:41 -0700 [thread overview]
Message-ID: <4FCCE9F5.9050808@fb.com> (raw)
In-Reply-To: <1338813658.28282.43.camel@twins>
On 6/4/12 5:40 AM, Peter Zijlstra wrote:
> And as a result you need that hideous prev_state crap.
>
>
> Would something like the below work?
>
> The one thing I'm not entirely sure of is if this is a sekjoerity issue
> or not.. anybody? I would think a task was entitled to know who woke it
> and wherefrom etc..
Frederic had some comments on this topic in the last round:
http://thread.gmane.org/gmane.linux.kernel/1195368/focus=1195959
> We should probably avoid the remote callchains, sounds like asking
for complications everywhere.
Do they still apply? Frederic?
-Arun
next prev parent reply other threads:[~2012-06-04 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 8:09 Andrew Vagin
2012-06-04 8:09 ` [PATCH 1/5] sched: event: add trace events when a task starts executing on a cpu Andrew Vagin
2012-06-04 8:09 ` [PATCH 2/5] sched: send the event sched_switch before perf_event_task_sched_out Andrew Vagin
2012-06-04 8:09 ` [PATCH 3/5] sched: save a previous state on task_struct Andrew Vagin
2012-06-04 8:09 ` [PATCH 4/5] perf: teach "perf inject" to work with files Andrew Vagin
2012-06-04 8:09 ` [PATCH 5/5] perf: teach perf inject to merge sched_switch* events for profiling sleep times Andrew Vagin
2012-06-04 12:40 ` [RFC] [PATCH 0/5] Teach perf tool to profile sleep times (V4) Peter Zijlstra
2012-06-04 12:50 ` Peter Zijlstra
2012-06-04 13:46 ` Steven Rostedt
2012-06-04 17:01 ` Arun Sharma [this message]
2012-06-04 20:52 ` Peter Zijlstra
2012-06-06 8:32 ` Ingo Molnar
2012-06-12 13:15 ` Andrew Wagin
2012-06-12 17:46 ` Peter Zijlstra
2012-06-04 17:03 ` Arun Sharma
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=4FCCE9F5.9050808@fb.com \
--to=asharma@fb.com \
--cc=OSTRIKOV@nvidia.com \
--cc=a.p.zijlstra@chello.nl \
--cc=avagin@openvz.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome