From: Borislav Petkov <bp@alien8.de>
To: Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>
Cc: linux-kernel@vger.kernel.org,
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>
Subject: Re: [PATCHv2] Support for perf on AMD family17h processors
Date: Thu, 17 Nov 2016 19:44:08 +0100 [thread overview]
Message-ID: <20161117184408.palimcvpqnru3aqs@pd.tnic> (raw)
In-Reply-To: <1479399306-13375-1-git-send-email-Janakarajan.Natarajan@amd.com>
On Thu, Nov 17, 2016 at 10:15:06AM -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.
>
> Signed-off-by: Janakarajan Natarajan <Janakarajan.Natarajan@amd.com>
> ---
>
> v1->v2
>
> * Removed renaming of amd_core_pmu_init and associated comment.
> * Changed comment style to follow guidelines.
>
> arch/x86/events/amd/core.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
I already ran your previous one today and since this one doesn't bring
any changes which matter:
Acked-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2016-11-17 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 16:15 [PATCHv2] Support for perf on AMD family17h processors Janakarajan Natarajan
2016-11-17 18:44 ` Borislav Petkov [this message]
2016-11-18 9:06 ` [tip:perf/urgent] perf/x86: Add perf support for AMD family-17h processors tip-bot for Janakarajan Natarajan
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=20161117184408.palimcvpqnru3aqs@pd.tnic \
--to=bp@alien8.de \
--cc=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 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.