From: Harish Chegondi <harish.chegondi@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
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 2/2] perf/x86/intel/uncore: Add Knights Landing uncore PMU support
Date: Wed, 9 Dec 2015 13:03:43 -0800 [thread overview]
Message-ID: <5668972F.5030805@intel.com> (raw)
In-Reply-To: <20151208090722.GH6356@twins.programming.kicks-ass.net>
On 12/08/2015 01:07 AM, Peter Zijlstra wrote:
> On Mon, Dec 07, 2015 at 02:32:32PM -0800, Harish Chegondi wrote:
>> @@ -981,6 +990,8 @@ static int __init uncore_pci_init(void)
>> break;
>> case 61: /* Broadwell */
>> ret = bdw_uncore_pci_init();
>> + case 87: /* Knights Landing */
>> + ret = knl_uncore_pci_init();
>> break;
>> default:
>> return 0;
>> @@ -1289,6 +1300,8 @@ static int __init uncore_cpu_init(void)
>> break;
>> case 86: /* BDX-DE */
>> bdx_uncore_cpu_init();
>> + case 87: /* Knights Landing */
>> + knl_uncore_cpu_init();
>> break;
>> default:
> Surely you need some extra break statements in there?
> .
>
Yes, I missed the break statements. I will add the breaks in the next version of the patch.
Thanks for the review!
-Harish.
next prev parent reply other threads:[~2015-12-09 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 22:32 [PATCH 1/2] perf/x86/intel/uncore: Remove hard coding of PMON box control MSR offset Harish Chegondi
2015-12-07 22:32 ` [PATCH 2/2] perf/x86/intel/uncore: Add Knights Landing uncore PMU support Harish Chegondi
2015-12-08 9:07 ` Peter Zijlstra
2015-12-09 21:03 ` Harish Chegondi [this message]
2015-12-09 23:37 ` Peter Zijlstra
2015-12-09 23:43 ` Harish Chegondi
2016-01-06 18:54 ` [tip:perf/core] " tip-bot for Harish Chegondi
2016-01-06 18:53 ` [tip:perf/core] perf/x86/intel/uncore: Remove hard coding of PMON box control MSR offset 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=5668972F.5030805@intel.com \
--to=harish.chegondi@intel.com \
--cc=andi.kleen@intel.com \
--cc=harish.chegondi@gmail.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.anaczkowski@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 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.