From: Michal Hocko <mhocko@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Artem S. Tashkinov" <t.artem@lycos.com>,
pomac@vapor.com, linux-kernel@vger.kernel.org,
tino.keitel@tikei.de
Subject: Re: [REGRESSION] [Linux 3.2] top/htop and all other CPU usage
Date: Wed, 30 Nov 2011 11:12:27 +0100 [thread overview]
Message-ID: <20111130101227.GA3187@tiehlicka.suse.cz> (raw)
In-Reply-To: <201111292351.16233.rjw@sisk.pl>
On Tue 29-11-11 23:51:16, Rafael J. Wysocki wrote:
> On Tuesday, November 29, 2011, Michal Hocko wrote:
> > On Tue 29-11-11 12:54:16, Artem S. Tashkinov wrote:
> > > > On Nov 29, 2011, Michal Hocko wrote:
> > > >
> > > > On Tue 29-11-11 13:31:56, Michal Hocko wrote:
> > > > > On Tue 29-11-11 11:38:47, Artem S. Tashkinov wrote:
> > > > [...]
> > > > > > $ grep . -r /sys/devices/system/cpu/cpuidle/
> > > > > > /sys/devices/system/cpu/cpuidle/current_driver:intel_idle
> > > > > > /sys/devices/system/cpu/cpuidle/current_governor_ro:menu
> > > >
> > > > Could you try with acpi_idle driver?
> > > > echo acpi_idle > /sys/devices/system/cpu/cpuidle/current_driver
> > >
> > > [root@localhost ~]# echo acpi_idle > /sys/devices/system/cpu/cpuidle/current_driver
> > > -bash: /sys/devices/system/cpu/cpuidle/current_driver: Permission denied
> >
> > It seems that this is cannot be set in runtime:
> > SYSDEV_CLASS_ATTR(current_driver, 0444, show_current_driver, NULL);
> >
> > Or maybe you need to boot with cpuidle_sysfs_switch. According to the
> > documentation you might be able to change the governor. I have no idea
> > whether this can help somehow but let's try that.
> >
> > I haven't found any intel_idle machine in my lab so far and all other
> > acpi_idle machines seem to work (or at least randomly selected ones) so
> > this smells like a major difference in the setup.
>
> I'm able to reproduce that with acpi_driver on one box, but not on demand.
And do you see the same thing (no idle/io_wait) updates?
>
> Thanks,
> Rafael
--
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
next prev parent reply other threads:[~2011-11-30 10:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 22:28 pomac
2011-11-29 7:52 ` Michal Hocko
2011-11-29 11:38 ` Artem S. Tashkinov
2011-11-29 12:31 ` Michal Hocko
2011-11-29 12:44 ` Michal Hocko
2011-11-29 12:54 ` Artem S. Tashkinov
2011-11-29 13:10 ` Michal Hocko
2011-11-29 13:51 ` Artem S. Tashkinov
2011-11-29 22:51 ` Rafael J. Wysocki
2011-11-30 10:12 ` Michal Hocko [this message]
2011-11-30 19:56 ` Rafael J. Wysocki
2011-12-01 14:07 ` Michal Hocko
2011-12-02 10:39 ` Michal Hocko
2011-12-02 13:35 ` Michal Hocko
2011-12-02 16:49 ` [PATCH] proc: Do not overflow get_{idle,iowait}_time for nohz (was: Re: Re: [REGRESSION] [Linux 3.2] top/htop and all other CPU usage) Michal Hocko
2011-12-02 17:59 ` Michal Hocko
2011-12-02 20:12 ` Artem S. Tashkinov
2011-12-05 8:56 ` Michal Hocko
2011-12-02 17:43 ` Re: Re: [REGRESSION] [Linux 3.2] top/htop and all other CPU usage Artem S. Tashkinov
2011-11-29 17:23 ` Ian Kumlien
2011-11-29 17:31 ` Ian Kumlien
2011-11-29 17:56 ` Michal Hocko
2011-11-29 18:37 ` Ian Kumlien
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=20111130101227.GA3187@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pomac@vapor.com \
--cc=rjw@sisk.pl \
--cc=t.artem@lycos.com \
--cc=tino.keitel@tikei.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 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®