From: Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>
To: <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>
Subject: [PATCH] Support for perf on AMD family17h processors
Date: Wed, 16 Nov 2016 11:01:53 -0600 [thread overview]
Message-ID: <1479315713-11115-1-git-send-email-Janakarajan.Natarajan@amd.com> (raw)
This patch enables perf core PMU support for AMD family17h processors.
In family17h, there is no PMC-event constraint. All events, irrespective
of the type, can be measured using any of the performance counters.
Signed-off-by: Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>
---
arch/x86/events/amd/core.c | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/arch/x86/events/amd/core.c b/arch/x86/events/amd/core.c
index f5f4b3f..849688d 100644
--- a/arch/x86/events/amd/core.c
+++ b/arch/x86/events/amd/core.c
@@ -652,7 +652,11 @@ static __initconst const struct x86_pmu amd_pmu = {
.amd_nb_constraints = 1,
};
-static int __init amd_core_pmu_init(void)
+/*
+ * This function initializes core PMU to enable support
+ * for AMD Core PMC Extension.
+ */
+static int __init amd_core_pmc_ext_init(void)
{
if (!boot_cpu_has(X86_FEATURE_PERFCTR_CORE))
return 0;
@@ -662,7 +666,12 @@ static int __init amd_core_pmu_init(void)
pr_cont("Fam15h ");
x86_pmu.get_event_constraints = amd_get_event_constraints_f15h;
break;
-
+ case 0x17:
+ pr_cont("Fam17h ");
+ /* In family 17h, there are no event constraints in the PMC hardware.
+ * We fallback to using default amd_get_event_constraints.
+ */
+ break;
default:
pr_err("core perfctr but no constraints; unknown hardware!\n");
return -ENODEV;
@@ -696,7 +705,7 @@ __init int amd_pmu_init(void)
x86_pmu = amd_pmu;
- ret = amd_core_pmu_init();
+ ret = amd_core_pmc_ext_init();
if (ret)
return ret;
--
2.7.4
next reply other threads:[~2016-11-16 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 17:01 Janakarajan Natarajan [this message]
2016-11-16 17:30 ` [PATCH] Support for perf on AMD family17h processors Peter Zijlstra
2016-11-16 20:41 ` Natarajan, Janakarajan
2016-11-16 18:47 ` Borislav Petkov
2016-11-16 20:49 ` Natarajan, Janakarajan
2016-11-17 6:46 ` Ingo Molnar
2016-11-17 15:50 ` Natarajan, Janakarajan
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=1479315713-11115-1-git-send-email-Janakarajan.Natarajan@amd.com \
--to=janakarajan.natarajan@amd.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=suravee.suthikulpanit@amd.com \
/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).