From: Ivor Hewitt <ivor@ivor.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: cpufreq@ZenII.linux.org.uk
Subject: Re: starting governor ondemand failed
Date: Mon, 04 Apr 2005 14:27:03 +0100 [thread overview]
Message-ID: <425140A7.6020804@ivor.org> (raw)
In-Reply-To: <20050404124304.GA17732@isilmar.linta.de>
Dominik Brodowski wrote:
> On Mon, Apr 04, 2005 at 11:42:19AM +0100, Ivor Hewitt wrote:
>
>>Hi,
>>I was trying to have a play with the ondemand governor but I just get
>>the following logged when I try to switch to it:-
>>
>>cpufreq-core: governor switch
>>cpufreq-core: __cpufreq_governor for CPU 0, event 2
>>userspace: managing cpu 0 stopped
>>cpufreq-core: __cpufreq_governor for CPU 0, event 1
>>cpufreq-core: starting governor ondemand failed
>>cpufreq-core: __cpufreq_governor for CPU 0, event 1
>>
>>This is on a PIIIM using the speedstep-smi interface.
>>The cpu is only capable of switching between two frequencies, would this
>>prevent ondemand starting up?
>
> This isn't the problem, but the following: we do not know how long
> transitions using speedstep-smi take, therefore we still need to assume
> that it takes very long, thus making it unable to be used for ondemand
> frequency switching.
>
Hi,
I'll stick to to cpufreqd then. :-)
Ah I see "CPUFREQ_ETERNAL".
What should be an acceptable transition time? Is it possible for me to
determine my speedstep-smi transition time and enable the switching?
Or are you saying that there's no way of knowing how long the smi
transition would take, therefore it has to be disabled?
Many thanks,
--
Ivor
http://www.ivor.it
next prev parent reply other threads:[~2005-04-04 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 10:42 starting governor ondemand failed Ivor Hewitt
2005-04-04 12:43 ` Dominik Brodowski
2005-04-04 13:27 ` Ivor Hewitt [this message]
2005-04-04 13:50 ` Ivor Hewitt
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 13:39 Pallipadi, Venkatesh
2005-04-04 16:58 ` Bruno Ducrot
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=425140A7.6020804@ivor.org \
--to=ivor@ivor.org \
--cc=cpufreq@ZenII.linux.org.uk \
--cc=linux@dominikbrodowski.net \
/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.