From: "Natarajan, Janakarajan" <Janakarajan.Natarajan@amd.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: <linux-kernel@vger.kernel.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>
Subject: Re: [PATCH] Support for perf on AMD family17h processors
Date: Wed, 16 Nov 2016 14:41:17 -0600 [thread overview]
Message-ID: <531d0b76-1668-4003-f844-fe751002a39c@amd.com> (raw)
In-Reply-To: <20161116173005.GW3142@twins.programming.kicks-ass.net>
On 11/16/2016 11:30 AM, Peter Zijlstra wrote:
> On Wed, Nov 16, 2016 at 11:01:53AM -0600, Janakarajan Natarajan wrote:
>> 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.
>>
> Is there a public document describing this thing about already?
There is no document published as of now.
>
>> + 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;
> http://lkml.kernel.org/r/CA+55aFyQYJerovMsSoSKS7PessZBr4vNp-3QUUwhqk4A4_jcbg@mail.gmail.com
I'll send out a v2 patch for the comment following the guidelines.
next prev parent reply other threads:[~2016-11-16 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 17:01 [PATCH] Support for perf on AMD family17h processors Janakarajan Natarajan
2016-11-16 17:30 ` Peter Zijlstra
2016-11-16 20:41 ` Natarajan, Janakarajan [this message]
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=531d0b76-1668-4003-f844-fe751002a39c@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).