From: skannan@codeaurora.org (Saravana Kannan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 2/2] perf/core: Add support for PMUs that can be read from any CPU
Date: Fri, 23 Feb 2018 16:56:37 -0800 [thread overview]
Message-ID: <5A90B845.3030504@codeaurora.org> (raw)
In-Reply-To: <1519431578-11995-2-git-send-email-skannan@codeaurora.org>
On 02/23/2018 04:19 PM, Saravana Kannan wrote:
> Some PMUs events can be read from any CPU. So allow the PMU to mark
> events as such. For these events, we don't need to reject reads or
> make smp calls to the event's CPU and cause unnecessary wake ups.
>
> Good examples of such events would be events from caches shared across
> all CPUs.
>
> Signed-off-by: Saravana Kannan <skannan@codeaurora.org>
> ---
> include/linux/perf_event.h | 3 +++
> kernel/events/core.c | 10 ++++++++--
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
>
Ugh! Didn't mean to chain these two emails. This one is independent of
the other email.
-Saravana
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Saravana Kannan <skannan@codeaurora.org>
To: Saravana Kannan <skannan@codeaurora.org>
Cc: mark.rutland@arm.com, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
avilaj@codeaurora.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] perf/core: Add support for PMUs that can be read from any CPU
Date: Fri, 23 Feb 2018 16:56:37 -0800 [thread overview]
Message-ID: <5A90B845.3030504@codeaurora.org> (raw)
In-Reply-To: <1519431578-11995-2-git-send-email-skannan@codeaurora.org>
On 02/23/2018 04:19 PM, Saravana Kannan wrote:
> Some PMUs events can be read from any CPU. So allow the PMU to mark
> events as such. For these events, we don't need to reject reads or
> make smp calls to the event's CPU and cause unnecessary wake ups.
>
> Good examples of such events would be events from caches shared across
> all CPUs.
>
> Signed-off-by: Saravana Kannan <skannan@codeaurora.org>
> ---
> include/linux/perf_event.h | 3 +++
> kernel/events/core.c | 10 ++++++++--
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
>
Ugh! Didn't mean to chain these two emails. This one is independent of
the other email.
-Saravana
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2018-02-24 0:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 0:19 [PATCH v1 1/2] perf/core: Add API to look up PMU type by name Saravana Kannan
2018-02-24 0:19 ` Saravana Kannan
2018-02-24 0:19 ` [PATCH v1 2/2] perf/core: Add support for PMUs that can be read from any CPU Saravana Kannan
2018-02-24 0:19 ` Saravana Kannan
2018-02-24 0:56 ` Saravana Kannan [this message]
2018-02-24 0:56 ` Saravana Kannan
2018-02-24 8:41 ` Peter Zijlstra
2018-02-24 8:41 ` Peter Zijlstra
2018-02-27 1:53 ` skannan at codeaurora.org
2018-02-27 1:53 ` skannan
2018-02-27 11:52 ` Mark Rutland
2018-02-27 11:52 ` Mark Rutland
2018-03-03 15:41 ` Peter Zijlstra
2018-03-03 15:41 ` Peter Zijlstra
2018-03-07 16:39 ` Jeremy Linton
2018-03-07 16:39 ` Jeremy Linton
2018-02-25 14:38 ` Mark Rutland
2018-02-25 14:38 ` Mark Rutland
2018-02-27 2:11 ` skannan at codeaurora.org
2018-02-27 2:11 ` skannan
2018-02-27 11:43 ` Mark Rutland
2018-02-27 11:43 ` Mark Rutland
2018-02-27 23:15 ` skannan at codeaurora.org
2018-02-27 23:15 ` skannan
2018-02-24 8:08 ` [PATCH v1 1/2] perf/core: Add API to look up PMU type by name Peter Zijlstra
2018-02-24 8:08 ` 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=5A90B845.3030504@codeaurora.org \
--to=skannan@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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.