From: Andi Kleen <ak@linux.intel.com>
To: kan.liang@intel.com
Cc: a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] perf/x86/intel: Broadwell support LBR callstack
Date: Thu, 2 Apr 2015 12:45:55 -0700 [thread overview]
Message-ID: <20150402194555.GD15335@tassilo.jf.intel.com> (raw)
In-Reply-To: <1427962377-40955-1-git-send-email-kan.liang@intel.com>
On Thu, Apr 02, 2015 at 04:12:57AM -0400, kan.liang@intel.com wrote:
> From: Kan Liang <kan.liang@intel.com>
>
> Same as Haswell, Broadwell also support LBR callstack.
>
> Signed-off-by: Kan Liang <kan.liang@intel.com>
Thanks looks good.
Acked-by: Andi Kleen <ak@linux.intel.com>
-Andi
> ---
> arch/x86/kernel/cpu/perf_event_intel.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/perf_event_intel.c b/arch/x86/kernel/cpu/perf_event_intel.c
> index fc6dbc4..4b61fe9 100644
> --- a/arch/x86/kernel/cpu/perf_event_intel.c
> +++ b/arch/x86/kernel/cpu/perf_event_intel.c
> @@ -2787,7 +2787,7 @@ __init int intel_pmu_init(void)
> hw_cache_extra_regs[C(NODE)][C(OP_WRITE)][C(RESULT_ACCESS)] = HSW_DEMAND_WRITE|
> BDW_L3_MISS_LOCAL|HSW_SNOOP_DRAM;
>
> - intel_pmu_lbr_init_snb();
> + intel_pmu_lbr_init_hsw();
>
> x86_pmu.event_constraints = intel_bdw_event_constraints;
> x86_pmu.pebs_constraints = intel_hsw_pebs_event_constraints;
> --
> 1.8.3.1
>
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2015-04-02 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 8:12 [PATCH 1/1] perf/x86/intel: Broadwell support LBR callstack kan.liang
2015-04-02 19:45 ` Andi Kleen [this message]
2015-04-18 10:14 ` [tip:perf/urgent] perf/x86/intel: Add Broadwell support for the " tip-bot for Kan Liang
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=20150402194555.GD15335@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.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