From: <suravee.suthikulpanit@amd.com>
To: <a.p.zijlstra@chello.nl>, <paulus@samba.org>, <mingo@redhat.com>,
<acme@ghostprotocols.net>, <tglx@linutronix.de>, <hpa@zytor.com>,
<rric@kernel.org>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <suravee.suthikulpanit@amd.com>, <jacob.shin@amd.com>
Subject: [PATCH 1/1] Change IBS PMU to use perf_hw_context
Date: Fri, 14 Dec 2012 14:57:42 -0600 [thread overview]
Message-ID: <1355518662-32071-1-git-send-email-suravee.suthikulpanit@amd.com> (raw)
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Currently, the AMD IBS PMU initialize pmu.task_ctx_nr to perf_invalid_context
which only allows IBS to be running only in system-wide mode (e.g. perf record -a).
IBS hardware is available in each core and should be per-context.
This patch modifies the task_ctx_nr to use the perf_hw_context (default) instead.
Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
diff --git a/arch/x86/kernel/cpu/perf_event_amd_ibs.c b/arch/x86/kernel/cpu/perf_event_amd_ibs.c
index 6336bcb..08fa71a 100644
--- a/arch/x86/kernel/cpu/perf_event_amd_ibs.c
+++ b/arch/x86/kernel/cpu/perf_event_amd_ibs.c
@@ -466,8 +466,6 @@ static struct attribute *ibs_op_format_attrs[] = {
static struct perf_ibs perf_ibs_fetch = {
.pmu = {
- .task_ctx_nr = perf_invalid_context,
-
.event_init = perf_ibs_init,
.add = perf_ibs_add,
.del = perf_ibs_del,
@@ -490,8 +488,6 @@ static struct perf_ibs perf_ibs_fetch = {
static struct perf_ibs perf_ibs_op = {
.pmu = {
- .task_ctx_nr = perf_invalid_context,
-
.event_init = perf_ibs_init,
.add = perf_ibs_add,
.del = perf_ibs_del,
--
1.7.10.4
next reply other threads:[~2012-12-14 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 20:57 suravee.suthikulpanit [this message]
2012-12-16 9:04 ` [PATCH 1/1] Change IBS PMU to use perf_hw_context Ingo Molnar
2012-12-17 9:44 ` Robert Richter
2012-12-18 22:54 ` Suravee Suthikulpanit
2013-01-16 22:19 ` Suravee Suthikulpanit
2013-06-18 16:03 ` Suravee Suthikulanit
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=1355518662-32071-1-git-send-email-suravee.suthikulpanit@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=hpa@zytor.com \
--cc=jacob.shin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=rric@kernel.org \
--cc=tglx@linutronix.de \
--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).