mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Artem S. Tashkinov" <t.artem@lycos.com>
Cc: linux-kernel@vger.kernel.org, dirk.j.brandewie@intel.com,
	cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
	dirk.brandewie@gmail.com
Subject: Re: CONFIG_X86_INTEL_PSTATE disables CPU frequency transition stats, many governors and other standard features
Date: Sat, 27 Apr 2013 16:35:59 +0200	[thread overview]
Message-ID: <1843018.F0kGJi5K1v@vostro.rjw.lan> (raw)
In-Reply-To: <475427035.74642.1367038733183.JavaMail.mail@webmail08>

On Saturday, April 27, 2013 04:58:53 AM Artem S. Tashkinov wrote:
> Hello,
> 
> Just wanted to let everyone know that CONFIG_X86_INTEL_PSTATE wreaks
> havoc with the CPU frequency subsystem in the Linux kernel.
> 
> With this option enabled:
> 
> 1) All governors except performance and powersave are gone, ondemand
> userspace, conservative
> 
> 2) scaling_cur_freq is gone, thus user space utilities monitoring the CPU
> frequency have stopped working
> 
> 3) CPU frequency transition stats are gone, there's no "stats" directory
> anywhere
> 
> 4) scaling_available_frequencies is gone, so I cannot set the desired constant
> CPU frequency (the userspace governor is not available anyway)
> 
> Is this an intended behavior? I shrivel to think that's the case.
> 
> The bug report is filed here: https://bugzilla.kernel.org/show_bug.cgi?id=57141

intel_pstate is not a usual cpufreq driver and from the cpufreq's perspective
it contains its own governor.  That's the reason why the other scaling governors
aren't available with it.

The sysfs attributes mentioned above are missing simply because they don't make
sense with intel_pstate.

I'm only wondering which user space doesn't work correctly with intel_pstate as
you said in the bug entry above.

If you don't want to use intel_pstate (in which case the ACPI driver will be
used instead), please append intel_pstate=disable to the kernel command line.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2013-04-27 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27  4:58 Artem S. Tashkinov
2013-04-27 14:35 ` Rafael J. Wysocki [this message]
2013-04-30  2:21   ` Andy Lutomirski
2013-04-30 15:54     ` Dirk Brandewie

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=1843018.F0kGJi5K1v@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=linux-pm@vger.kernel.org \
    --cc=t.artem@lycos.com \
    /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®