mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: dirk.brandewie@gmail.com, linux-kernel@vger.kernel.org,
	cpufreq@vger.kernel.org,
	Dirk Brandewie <dirk.j.brandewie@intel.com>
Subject: Re: [PATCH] cpufreq/intel_pstate: Add kernel command line option disable intel_pstate.
Date: Fri, 15 Feb 2013 13:30:50 +0100	[thread overview]
Message-ID: <2881062.pPx9cdkTcn@vostro.rjw.lan> (raw)
In-Reply-To: <CAOh2x=mH0k8ZB0Qq+q=2bxwHcMUVmj-cy-=N4dBf=6Q2xd6nMw@mail.gmail.com>

On Friday, February 15, 2013 09:53:24 AM Viresh Kumar wrote:
> On Fri, Feb 15, 2013 at 12:08 AM,  <dirk.brandewie@gmail.com> wrote:
> > From: Dirk Brandewie <dirk.brandewie@gmail.com>
> >
> > When intel_pstate is configured into the kernel it will become the
> > perferred scaling driver for processors that is supports.  Allow the
> 
> s/perferred/preferred
> 
> s/is/it
> 
> > user to override this by adding:
> >    intel_pstate=disable
> > on the kernel command line.
> >
> > Signed-off-by: Dirk Brandewie <dirk.j.brandewie@intel.com>
> > ---
> >  Documentation/kernel-parameters.txt |    5 +++++
> >  drivers/cpufreq/intel_pstate.c      |   16 ++++++++++++++++
> >  2 files changed, 21 insertions(+), 0 deletions(-)
> >
> > diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> > index 6c72381..41c5d9e 100644
> > --- a/Documentation/kernel-parameters.txt
> > +++ b/Documentation/kernel-parameters.txt
> > @@ -1131,6 +1131,11 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
> >                         0       disables intel_idle and fall back on acpi_idle.
> >                         1 to 6  specify maximum depth of C-state.
> >
> > +       intel_pstate=  [X86]
> > +                      disable
> > +                        Do not enable intel_pstate as the default
> > +                        scaling driver for the supported processors
> > +
> >         intremap=       [X86-64, Intel-IOMMU]
> >                         on      enable Interrupt Remapping (default)
> >                         off     disable Interrupt Remapping
> > diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
> > index e879963..9cbb733 100644
> > --- a/drivers/cpufreq/intel_pstate.c
> > +++ b/drivers/cpufreq/intel_pstate.c
> > @@ -773,11 +773,16 @@ static void intel_pstate_exit(void)
> >  }
> >  module_exit(intel_pstate_exit);
> >
> > +static int no_load;
> > +
> >  static int __init intel_pstate_init(void)
> >  {
> >         int rc = 0;
> >         const struct x86_cpu_id *id;
> >
> > +       if (no_load)
> > +               return -ENODEV;
> > +
> >         id = x86_match_cpu(intel_pstate_cpu_ids);
> >         if (!id)
> >                 return -ENODEV;
> > @@ -802,6 +807,17 @@ out:
> >  }
> >  device_initcall(intel_pstate_init);
> >
> > +static int __init intel_pstate_setup(char *str)
> 
> Parameter to this is really not required. By default intel_pstate
> driver is enabled, so just past disable_intel_pstate from command line
> without any args.

Well, quite frankly, I'm fine with both.  It all boils down to passing a
specific string on the kernel command line.

Thanks,
Rafael


> > +{
> > +       if (!str)
> > +               return -EINVAL;
> > +
> > +       if (!strcmp(str, "disable"))
> > +               no_load = 1;
> > +       return 0;
> > +}
> > +early_param("intel_pstate", intel_pstate_setup);
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2013-02-15 12:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 17:02 [PATCH 0/5] Add P state driver for Intel Core Processors dirk.brandewie
2013-02-06 17:02 ` [PATCH 1/5] cpufreq: Retrieve current frequency from scaling drivers with internal governors dirk.brandewie
2013-02-07 13:46   ` Viresh Kumar
2013-02-06 17:02 ` [PATCH 2/5] cpufreq: Only call cpufreq_out_of_sync() for driver that implement cpufreq_driver.target() dirk.brandewie
2013-02-06 17:02 ` [PATCH 2/5] cpufreq: Only call cpufreq_out_of_sync() with drivers " dirk.brandewie
2013-02-07 10:33   ` Viresh Kumar
2013-02-06 17:02 ` [PATCH 3/5] cpufreq: Do not track governor name for scaling drivers with internal governors dirk.brandewie
2013-02-07 10:43   ` Viresh Kumar
2013-02-07 13:45   ` Viresh Kumar
2013-02-06 17:02 ` [PATCH 4/5] cpufreq_stats: do not remove sysfs files if frequency table is not present dirk.brandewie
2013-02-06 17:02 ` [PATCH 5/5] cpufreq/x86: Add P-state driver for sandy bridge dirk.brandewie
2013-02-07 14:01   ` Viresh Kumar
2013-02-07 10:42 ` [PATCH 0/5] Add P state driver for Intel Core Processors Viresh Kumar
2013-02-07 14:02   ` Viresh Kumar
2013-02-07 22:43     ` Rafael J. Wysocki
2013-02-12 21:49 ` Dave Jones
2013-02-13 16:38   ` Dirk Brandewie
2013-02-13 21:17     ` Rafael J. Wysocki
2013-02-14 18:38       ` [PATCH] cpufreq/intel_pstate: Add kernel command line option disable intel_pstate dirk.brandewie
2013-02-14 22:56         ` Yinghai Lu
2013-02-15  4:23         ` Viresh Kumar
2013-02-15 12:30           ` Rafael J. Wysocki [this message]
2013-02-15 13:28             ` Viresh Kumar
2013-02-15 16:12               ` Dirk Brandewie
2013-02-15 16:15       ` dirk.brandewie
2013-02-14  4:08     ` [PATCH 0/5] Add P state driver for Intel Core Processors Viresh Kumar
2013-02-14 12:21       ` Rafael J. Wysocki
2013-02-14 15:23         ` Dirk Brandewie
2013-02-14 15:34         ` Dirk Brandewie
2013-02-14 17:36           ` Rafael J. Wysocki
2013-02-13 20:14   ` [PATCH] cpufreq/intel_pstate: Change to disallow module build dirk.brandewie
2013-02-13 20:14     ` dirk.brandewie
2013-02-14 16:10     ` Viresh Kumar

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=2881062.pPx9cdkTcn@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=dirk.brandewie@gmail.com \
    --cc=dirk.j.brandewie@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viresh.kumar@linaro.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

all inboxes | Powered by JetHome®