From: Peter Zijlstra <peterz@infradead.org>
To: Harish Chegondi <harish.chegondi@intel.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
Harish Chegondi <harish.chegondi@gmail.com>,
Andi Kleen <andi.kleen@intel.com>,
Kan Liang <kan.liang@intel.com>,
Lukasz Anaczkowski <lukasz.anaczkowski@intel.com>
Subject: Re: [PATCH 1/1] perf/x86/intel: Add perf core PMU support for Intel Knights Landing
Date: Tue, 8 Dec 2015 09:37:57 +0100 [thread overview]
Message-ID: <20151208083757.GD6356@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <d14593c7311f78c93c9cf6b006be843777c5ad5c.1449517401.git.harish.chegondi@intel.com>
On Mon, Dec 07, 2015 at 02:28:18PM -0800, Harish Chegondi wrote:
> Knights Landing core is based on Silvermont core with several differences.
> Like Silvermont, Knights Landing has 8 pairs of LBR MSRs. However, the
> LBR MSRs addresses match those of the Xeon cores' first 8 pairs of LBR MSRs
> +/* Knights Landing */
> +void intel_pmu_lbr_init_knl(void)
> +{
> + x86_pmu.lbr_nr = 8;
> + x86_pmu.lbr_tos = MSR_LBR_TOS;
> + x86_pmu.lbr_from = MSR_LBR_NHM_FROM;
> + x86_pmu.lbr_to = MSR_LBR_NHM_TO;
> +
> + x86_pmu.lbr_sel_mask = LBR_SEL_MASK;
> + x86_pmu.lbr_sel_map = snb_lbr_sel_map;
Also, unlike Silvermont, this thing seems to have hardware LBR filters.
So would it not be more accurate to say the KNL has a big core LBR
instead? (Note that this LBR setup isn't specific to Xeon's, all of the
Core chips have this, including the client parts).
> + pr_cont("8-deep LBR, ");
> +}
next prev parent reply other threads:[~2015-12-08 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 22:28 [PATCH 1/1] perf/x86/intel: Add perf core PMU support for Intel Knights Landing Harish Chegondi
2015-12-08 8:37 ` Peter Zijlstra [this message]
2015-12-09 23:22 ` Harish Chegondi
2015-12-09 23:37 ` Peter Zijlstra
2015-12-09 23:42 ` Harish Chegondi
2016-01-06 18:53 ` [tip:perf/core] " tip-bot for Harish Chegondi
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=20151208083757.GD6356@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andi.kleen@intel.com \
--cc=harish.chegondi@gmail.com \
--cc=harish.chegondi@intel.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.anaczkowski@intel.com \
--cc=mingo@redhat.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