From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andrew Vagin <avagin@openvz.org>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>, Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH 2/4] trace: prepare to collect call chains of non-current task.
Date: Tue, 27 Sep 2011 16:02:31 +0200 [thread overview]
Message-ID: <1317132151.15383.64.camel@twins> (raw)
In-Reply-To: <1317052535-1765247-3-git-send-email-avagin@openvz.org>
On Mon, 2011-09-26 at 19:55 +0400, Andrew Vagin wrote:
> +perf_callchain_kernel(struct perf_callchain_entry *entry,
> + struct task_struct *tsk, struct pt_regs *regs)
Hmm, we have event->ctx->task, but I guess for per-cpu events that's
useless..
next prev parent reply other threads:[~2011-09-27 14:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 15:55 [PATCH 0/4] trace: add ability to collect call chains of non-current task Andrew Vagin
2011-09-26 15:55 ` [PATCH 1/4] perf: fix counter of ftrace events Andrew Vagin
2011-10-14 19:11 ` Arun Sharma
2011-09-26 15:55 ` [PATCH 2/4] trace: prepare to collect call chains of non-current task Andrew Vagin
2011-09-27 14:02 ` Peter Zijlstra [this message]
2011-10-14 19:12 ` Arun Sharma
2011-09-26 15:55 ` [PATCH 3/4] trace: add ability to collect call chain " Andrew Vagin
2011-09-27 14:05 ` Peter Zijlstra
2011-09-27 20:55 ` Frederic Weisbecker
2011-09-28 13:53 ` Andrew Vagin
2011-12-08 2:02 ` Arun Sharma
2011-12-09 11:07 ` Andrey Vagin
2011-12-14 20:14 ` Arun Sharma
2011-12-15 15:19 ` Andrew Vagin
2011-12-15 19:08 ` Arun Sharma
2011-12-16 0:15 ` Arun Sharma
2011-09-26 15:55 ` [PATCH 4/4] events: sched_stat_template saves call chains of a target task Andrew Vagin
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=1317132151.15383.64.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=avagin@openvz.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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