From: David Carrillo-Cisneros <davidcc@google.com>
To: linux-kernel@vger.kernel.org
Cc: "x86@kernel.org" <x86@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <ak@linux.intel.com>, Kan Liang <kan.liang@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Vegard Nossum <vegard.nossum@gmail.com>,
Paul Turner <pjt@google.com>,
Stephane Eranian <eranian@google.com>,
David Carrillo-Cisneros <davidcc@google.com>
Subject: [PATCH v2 0/4] remove unnecessary IPI reading uncore events
Date: Sat, 6 Aug 2016 20:12:53 -0700 [thread overview]
Message-ID: <1470539577-102094-1-git-send-email-davidcc@google.com> (raw)
This patch series adds a new flag to the struct perf_event
(and a flag field to store it) to allow a PMU to tag a CPU or
cgroup event as readable from any CPU in the same package and not
just the CPU where the is currently active.
This capability is used with uncore events to potentially avoid
an unnecessary IPI when executing perf_event_read.
A previous version of this change was introduced in the last Intel's
CQM/CMT driver series (under review), but now we present it separately
here since it is also useful for other uncore events.
The next version of Intel CQM/CMT will add 3 new flags that use
the pmu_event_flags field (added in patch 03 in this series).
Patch 02 generalizes event->group_flags so that new flags can use it
in a similar way that PERF_GROUP_SOFTWARE was used.
Patches rebased at peterz/queue/perf/core
Changes in v2:
- Change logic to use event->group_flags instead of individually
testing sibling in perf_event_read.
- Remove erroneous read of inactive events.
David Carrillo-Cisneros (4):
perf/core: check return value of perf_event_read IPI
perf/core: generalize event->group_flags
perf/core: introduce PMU_EV_CAP_READ_ACTIVE_PKG
perf/x86: use PMUEF_READ_CPU_PKG in uncore events
arch/x86/events/intel/rapl.c | 2 ++
arch/x86/events/intel/uncore.c | 2 ++
arch/x86/events/intel/uncore_snb.c | 2 ++
include/linux/perf_event.h | 21 +++++++++++----
kernel/events/core.c | 52 +++++++++++++++++++++++++-------------
5 files changed, 57 insertions(+), 22 deletions(-)
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-08-07 3:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 3:12 David Carrillo-Cisneros [this message]
2016-08-07 3:12 ` [PATCH v2 1/4] perf/core: check return value of perf_event_read IPI David Carrillo-Cisneros
2016-08-10 11:04 ` Ingo Molnar
2016-08-17 20:53 ` David Carrillo-Cisneros
2016-08-07 3:12 ` [PATCH v2 2/4] perf/core: generalize event->group_flags David Carrillo-Cisneros
2016-08-07 3:12 ` [PATCH v2 3/4] perf/core: introduce PMU_EV_CAP_READ_ACTIVE_PKG David Carrillo-Cisneros
2016-08-07 19:10 ` Nilay Vaish
2016-08-07 20:10 ` David Carrillo-Cisneros
2016-08-08 16:12 ` Nilay Vaish
2016-08-09 5:04 ` David Carrillo-Cisneros
2016-08-09 22:28 ` [PATCH " David Carrillo-Cisneros
2016-08-10 18:27 ` Nilay Vaish
2016-08-08 10:00 ` [PATCH v3 " David Carrillo-Cisneros
2016-08-07 3:12 ` [PATCH v2 4/4] perf/x86: use PMUEF_READ_CPU_PKG in uncore events David Carrillo-Cisneros
2016-08-10 18:30 ` [PATCH v2 0/4] remove unnecessary IPI reading " Nilay Vaish
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=1470539577-102094-1-git-send-email-davidcc@google.com \
--to=davidcc@google.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@gmail.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).