From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Aaron Lu <aaron.lu@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG cpufreq] Invalid argument on writing to scaling_governor
Date: Fri, 01 Aug 2014 14:47:53 +0200 [thread overview]
Message-ID: <3664850.5ao49mLJsS@vostro.rjw.lan> (raw)
In-Reply-To: <53DB701B.9070900@redhat.com>
On Friday, August 01, 2014 06:46:51 AM Prarit Bhargava wrote:
>
> On 08/01/2014 06:43 AM, Fengguang Wu wrote:
> > Hi Prarit,
> >
> > I noticed that commit dbcbfe6aa0d61ae5e13cab43b30802482007c199 ("cpufreq: hold
> > policy->rwsem for duration of changing governors") will cause this problem:
> >
> > root@nhm4 ~# echo performance > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
> > -bash: echo: write error: Invalid argument
> >
> > root@nhm4 ~# cat /sys/devices/system/cpu/cpu3/cpufreq/scaling_available_governors
> > conservative userspace powersave ondemand performance
> >
>
> Rafael, this patch needs to be rejected based on my previous comments, most
> notably Saravana was able to reproduce the original problem. I'm going to wait
> for his reproducer and see what I can do.
I've dropped it already. At least as far as I can say it shouldn't be there in
my linux-next branch any more. Can you double check, please?
Rafael
prev parent reply other threads:[~2014-08-01 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 10:43 [BUG cpufreq] Invalid argument on writing to scaling_governor Fengguang Wu
2014-08-01 10:46 ` Prarit Bhargava
2014-08-01 12:47 ` Rafael J. Wysocki [this message]
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=3664850.5ao49mLJsS@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=aaron.lu@intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=rafael.j.wysocki@intel.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 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.