All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Harry van Haaren <harryhaaren@gmail.com>
Cc: linux-rt-users@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: CpuFreq Laptop Scaling broken?
Date: Tue, 26 Aug 2014 10:04:26 +0530	[thread overview]
Message-ID: <CAKohpokc+PiviEt3_2h0JjiH-XUuxiR5Tt6=NnJqTrCL_i98sA@mail.gmail.com> (raw)
In-Reply-To: <CAKudYbNNA3TLR0gyesiwy_38AtjNgf4bVjgd7+rguLxiVHCzUw@mail.gmail.com>

On 25 August 2014 19:32, Harry van Haaren <harryhaaren@gmail.com> wrote:
> On Mon, Aug 25, 2014 at 2:55 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>> You tried both these as root? Even 'sudo' may not work..
> Yes, the original output was all as root (not sudo, genuine root).
>
>> I haven't seen the rt code since sometime, what tag should I look at ?
> I'm running 3.14.12-rt9-1-rt  (as packaged for Arch here:
> https://aur.archlinux.org/packages/linux-rt )

I don't have a clue of what's going wrong here..

But my guess would be that something is not working with locking, as that's
one of the main difference between rt and non-rt kernels.

Can you try to debug it with some prints?

The functions  of interest would be, drivers/cpufreq/cpufreq.c:
- static ssize_t show(struct kobject *kobj, struct attribute *attr, char *buf)
- static ssize_t store_scaling_governor(struct cpufreq_policy *policy,
const char *buf, size_t count)

Try to add some prints there while returning errors and then try to change
governor from userspace and things might get somewhat better then..

--
viresh

  parent reply	other threads:[~2014-08-26  4:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25 12:28 CpuFreq Laptop Scaling broken? Harry van Haaren
2014-08-25 13:55 ` Viresh Kumar
2014-08-25 13:56   ` Viresh Kumar
2014-08-25 16:58     ` Joakim Hernberg
2014-08-25 14:02   ` Harry van Haaren
2014-08-25 17:18     ` Fernando Lopez-Lezcano
2014-08-25 17:36       ` Harry van Haaren
2014-08-26  4:34     ` Viresh Kumar [this message]
2014-08-26 22:44       ` Harry van Haaren
2014-08-27 14:53         ` Harry van Haaren
     [not found]           ` <CAKohpokeUufzx7so6FcEd8rAg-MPw+2c9Aug9L_vXdu_4MvNOA@mail.gmail.com>
2014-09-05 12:06             ` Harry van Haaren
2014-09-05 12:50               ` Viresh Kumar
2014-09-05 22:47                 ` Thomas Gleixner
2014-09-25 12:44                   ` Harry van Haaren
2014-08-25 14:10   ` Steven Rostedt
     [not found]     ` <53FB4EEF.3060809@pavlinux.ru>
2014-08-25 15:03       ` Harry van Haaren

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='CAKohpokc+PiviEt3_2h0JjiH-XUuxiR5Tt6=NnJqTrCL_i98sA@mail.gmail.com' \
    --to=viresh.kumar@linaro.org \
    --cc=harryhaaren@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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.