From: Peter Zijlstra <peterz@infradead.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ye olde task_ctx_sched_out trace.
Date: Thu, 22 May 2014 09:22:22 +0200 [thread overview]
Message-ID: <20140522072222.GR30445@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <537D9EBE.7030806@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
On Thu, May 22, 2014 at 09:52:46AM +0300, Adrian Hunter wrote:
> +/*
> + * PERF_RECORD_MISC_MMAP_DATA and PERF_RECORD_MISC_COMM_EXEC are used on
> + * different events so can reuse the same bit position.
> + */
> #define PERF_RECORD_MISC_MMAP_DATA (1 << 13)
> +#define PERF_RECORD_MISC_COMM_EXEC (1 << 13)
> /*
> * Indicates that the content of PERF_SAMPLE_IP points to
> * the actual instruction that triggered the event. See also
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index ed50b09..760abd0 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -5067,7 +5067,7 @@ static void perf_event_comm_event(struct perf_comm_event *comm_event)
> NULL);
> }
>
> -void perf_event_comm(struct task_struct *task)
> +void perf_event_comm(struct task_struct *task, bool exec)
> {
> struct perf_comm_event comm_event;
> struct perf_event_context *ctx;
> @@ -5093,7 +5093,7 @@ void perf_event_comm(struct task_struct *task)
> .event_id = {
> .header = {
> .type = PERF_RECORD_COMM,
> - .misc = 0,
> + .misc = exec ? PERF_RECORD_MISC_COMM_EXEC : 0,
> /* .size */
> },
> /* .pid */
OK, now that you pointed out the obvious, yeah, I suppose we can do that :-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-22 7:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 15:06 Dave Jones
2014-05-21 15:16 ` Peter Zijlstra
2014-05-21 15:30 ` Peter Zijlstra
2014-05-21 15:32 ` Peter Zijlstra
2014-05-22 6:52 ` Adrian Hunter
2014-05-22 7:04 ` Peter Zijlstra
2014-05-22 7:10 ` Adrian Hunter
2014-05-22 7:20 ` Peter Zijlstra
2014-05-22 7:22 ` Peter Zijlstra [this message]
2014-05-28 8:02 ` Adrian Hunter
2014-06-06 12:19 ` [tip:perf/core] perf: Differentiate exec() and non-exec() comm events tip-bot for Adrian Hunter
2014-06-06 12:19 ` [tip:perf/core] perf: Fix perf_event_comm() vs. exec() assumption 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=20140522072222.GR30445@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.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