From: Peter Zijlstra <peterz@infradead.org>
To: Harry Pan <harry.pan@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
gs0622@gmail.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, bp@alien8.de,
srinivas.pandruvada@linux.intel.com, ray.huang@amd.com
Subject: Re: [PATCH 2/2] perf/x86/rapl: Enable Baytrail/Braswell RAPL support
Date: Fri, 9 Sep 2016 11:29:08 +0200 [thread overview]
Message-ID: <20160909092908.GG10153@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1473325738-730-2-git-send-email-harry.pan@intel.com>
On Thu, Sep 08, 2016 at 05:08:58PM +0800, Harry Pan wrote:
> @@ -177,6 +187,16 @@ static inline u64 rapl_scale(u64 v, int cfg)
> pr_warn("Invalid domain %d, failed to scale data\n", cfg);
> return v;
> }
> +
> + /*
> + * Some Atom series processors (BYT/BSW) use 2^ESU microjoules.
> + *
> + * TODO: this looks hacky, it's better to refactor scale-up mechanism
> + * to compromise the main stream processors and Atom ones.
> + */
> + if (is_baytrail)
> + return v << rapl_hw_unit[cfg - 1];
> +
Can't you simply set rapl_hw_unit[] such that 32 - rapl_hw_unit[] ends
up at the right number? Then you only get to much with values in
rapl_check_hw_unit without runtime overhead later.
> +static int rapl_check_hw_unit(enum rapl_quirk apply_quirk)
> {
> u64 msr_rapl_power_unit_bits;
> int i;
> @@ -634,10 +674,20 @@ static int rapl_check_hw_unit(bool apply_quirk)
> * "Intel Xeon Processor E5-1600 and E5-2600 v3 Product Families, V2
> * of 2. Datasheet, September 2014, Reference Number: 330784-001 "
> */
> - if (apply_quirk)
> + if (apply_quirk == RAPL_HSX_QUIRK)
> rapl_hw_unit[RAPL_IDX_RAM_NRG_STAT] = 16;
>
> /*
> + * Some Atom processors (BYT/BSW) have 2^ESU microjoules increment,
> + * refer to Software Developers' Manual, Vol. 3C, Order No. 325384,
> + * Table 35-8 of MSR_RAPL_POWER_UNIT
> + */
> + if (apply_quirk == RAPL_BYT_QUIRK)
> + is_baytrail = true;
> + else
> + is_baytrail = false;
it was already false...
/*
* comment explaining quirk goes here...
*/
if (apply_quirk = RAPL_BYT_QUIRK) {
for (i = 0; i < NR_RAPL_DOMAINS; i++)
rapl_hw_unit[i] = 32 - rapl_hw_unit[i];
}
and then you get to verify what to do with rapl_timer_ms.
> static const struct intel_rapl_init_fun snb_rapl_init __initconst = {
> - .apply_quirk = false,
> + .apply_quirk = 0,
Either leave it out (unmentioned members get initialized to 0) or add
RAPL_NO_QUIRK or so.
> .cntr_mask = RAPL_IDX_CLN,
> .attrs = rapl_events_cln_attr,
> };
>
next prev parent reply other threads:[~2016-09-09 9:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 9:08 [PATCH 1/2] perf/x86/rapl: Enable Apollo Lake " Harry Pan
2016-09-08 9:08 ` [PATCH 2/2] perf/x86/rapl: Enable Baytrail/Braswell " Harry Pan
2016-09-09 9:29 ` Peter Zijlstra [this message]
2016-09-09 15:08 ` Pan, Harry
2016-09-10 12:42 ` [tip:perf/core] perf/x86/rapl: Enable Apollo Lake " tip-bot for Harry Pan
2016-09-09 15:01 [PATCH 1/2] " Harry Pan
2016-09-09 15:01 ` [PATCH 2/2] perf/x86/rapl: Enable Baytrail/Braswell " Harry Pan
2016-09-09 15:11 ` Thomas Gleixner
2016-09-09 17:59 ` Pan, Harry
2016-09-09 21:21 ` Thomas Gleixner
2016-09-11 3:06 ` Pan, Harry
2016-09-11 5:38 ` Pan, Harry
2016-09-09 17:53 [PATCH 1/2] perf/x86/rapl: Enable Apollo Lake " Harry Pan
2016-09-09 17:53 ` [PATCH 2/2] perf/x86/rapl: Enable Baytrail/Braswell " Harry Pan
2016-09-09 21:02 ` kbuild test robot
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=20160909092908.GG10153@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=gs0622@gmail.com \
--cc=harry.pan@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ray.huang@amd.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=x86@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
Powered by JetHome