From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Darren Hart <dvhart@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform: x86: Support Turbo Boost Max for non HWP systems
Date: Tue, 17 Jan 2017 16:39:21 -0800 [thread overview]
Message-ID: <1484699961.3886.42.camel@linux.intel.com> (raw)
In-Reply-To: <20170118003227.GC2599@wisp>
On Tue, 2017-01-17 at 16:32 -0800, Darren Hart wrote:
> On Wed, Jan 11, 2017 at 12:36:34PM -0800, Srinivas Pandruvada wrote:
> >
> > On platforms supporting Intel Turbo Boost Max Technology 3.0, the
> > maximum turbo frequencies (turbo ratio) of some cores in a CPU
> > package
> > may be higher than the other cores in the same package. In that
> > case,
> > better performance can be achieved by making the scheduler prefer
> > to run
> > tasks on the CPUs with higher max turbo frequencies.
> >
> > On Intel® Broadwell Xeon systems, it is optional to turn on HWP
> > (Hardware P-States). When HWP is not turned on, the BIOS doesn't
> > present required CPPC (Collaborative Processor Performance Control)
> > tables. This table is used to get the per CPU core maximum
> > performance
> > ratio and inform scheduler (in cpufreq/intel_pstate driver).
> >
> > On such systems the maximum performance ratio can be read via over
> > clocking (OC) mailbox interface for each CPU. This interface is not
> > architectural and can change for every model of processors.
> >
> > This driver reads maximum performance ratio of each CPU and set up
> > the scheduler priority metrics. In this way scheduler can prefer
> > CPU
> > with higher performance to schedule tasks.
> >
> > Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel
> > .com>
>
> Thanks Srinivas,
>
> Driver queued to testing with the following changes, but see below...
>
> diff --git a/drivers/platform/x86/intel_turbo_boost_max_enum.c
> b/drivers/platform/x86/intel_turbo_boost_max_enum.c
> index 5ad3257..5df43c9 100644
> --- a/drivers/platform/x86/intel_turbo_boost_max_enum.c
> +++ b/drivers/platform/x86/intel_turbo_boost_max_enum.c
> @@ -1,6 +1,7 @@
> /*
> * Intel Turbo Boost Max Technology 3.0 legacy (non HWP) enumeration
> driver
> * Copyright (c) 2017, Intel Corporation.
> + * All rights reserved.
>
> This is the preferred format last time I asked Intel legal.
>
> *
> * This program is free software; you can redistribute it and/or
> modify it
> * under the terms and conditions of the GNU General Public License,
> @@ -37,10 +38,8 @@
>
> static int get_oc_core_priority(unsigned int cpu)
> {
> - u64 value;
> - u64 cmd = OC_MAILBOX_FC_CONTROL_CMD;
> - int i;
> - int ret;
> + u64 value, cmd = OC_MAILBOX_FC_CONTROL_CMD;
> + int ret, i;
>
> Subjective, but we prefer to save the lines.
>
> /* Issue favored core read command */
> value = cmd << MSR_OC_MAILBOX_CMD_OFFSET;
>
>
> >
> > ---
> > drivers/platform/x86/Kconfig | 10 ++
> > drivers/platform/x86/Makefile | 1 +
> > drivers/platform/x86/intel_turbo_boost_max_enum.c | 153
> > ++++++++++++++++++++++
>
> Regarding the name, two nits:
>
> 1) It's soooooooooooooooo long..... and the CONFIG_* too.
> 2) Since it is BDW specifc, how about:
>
> intel_bdw_turbo.c
> CONFIG_INTEL_BDW_TURBO
We should add _MAX_3 as this is a technology more than simple TURBO.
CONFIG_INTEL_BDW_TURBO_MAX_3
>
> I don't think "max enumeration" conveys any meaning to most readers.
>
> Thoughts?
Fine with me with the above comment.
Thanks,
Srinivas
next prev parent reply other threads:[~2017-01-18 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 20:36 [PATCH] platform: x86: Support Turbo Boost Max for non HWP systems Srinivas Pandruvada
2017-01-18 0:32 ` Darren Hart
2017-01-18 0:39 ` Srinivas Pandruvada [this message]
2017-01-18 3:24 ` Andy Shevchenko
2017-01-18 16:31 ` Srinivas Pandruvada
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=1484699961.3886.42.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=dvhart@infradead.org \
--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 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.