cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.de>
To: holbling@cpt.univ-mrs.fr, davej@codemonkey.org.uk
Cc: Bruno Ducrot <ducrot@poupinou.org>, cpufreq@www.linux.org.uk
Subject: Re: [PATCH] 2.6.5 speedstep on P4Ms
Date: Thu, 10 Jun 2004 10:30:38 +0200	[thread overview]
Message-ID: <20040610083038.GA18693@dominikbrodowski.de> (raw)
In-Reply-To: <40C7AF6C.1080408@cern.ch>


[-- Attachment #1.1: Type: text/plain, Size: 1260 bytes --]

> i also wonder about one thing, maybe you can help me on that. with the 
> old speedstep driver,
Do you mean speedstep-smi? Or what driver did you use?

> i would have occational hard freezups of my 
> machine. this seems to be gone (just experimental evidence, since i 
> didn't have one in a few days now where before they occured about 
> hourly). so my guess is that something in this patch must have corrected 
> it. since my machine just has one physical cpu, i really don't 
> understand what went wrong before.  do you have any idea on that?

Depends on the driver you were using :-)

> as far as i understand, the frequencies are always the same, because the 
> siblings are explicitly notified. about the 2 different governors, the 
> same problem exists in the current p4-clockmod.
> 
> >I'll try to fix it in the 2.6.8 timeframe...
> > 
> >
> you mean that a change of governors gets communicated to the siblings?

I mean that only one instance of a governor can be loaded on one physical
CPU. The same problem exists in current p4-clockmod and was a mis-design of
the cpufreq core [by me...], so it needs to be fixed quite soon.

Both patches look good to me -- Dave, could you apply them, please?

Thanks,
	Dominik

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq

  reply	other threads:[~2004-06-10  8:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 17:15 [PATCH] 2.6.5 speedstep on P4Ms Christian Hoelbling
2004-06-08 15:30 ` Bruno Ducrot
2004-06-08 23:53   ` Christian Hoelbling
2004-06-09 15:47     ` Dominik Brodowski
2004-06-09 16:09       ` Bruno Ducrot
2004-06-09 16:29       ` Dave Jones
2004-06-09 16:53         ` Dominik Brodowski
2004-06-09 18:32           ` Mattia Dongili
2004-06-10  0:46       ` Christian Hoelbling
2004-06-10  8:30         ` Dominik Brodowski [this message]
2004-06-10 11:20           ` Dave Jones
2004-06-10  9:10         ` Bruno Ducrot
2004-06-10 15:37         ` Bruno Ducrot
2004-06-10 16:44           ` Dominik Brodowski
2004-06-10 19:26             ` [PATCH] Remove notify in speedstep_set_state [1/2] Bruno Ducrot
2004-06-10 19:28             ` [PATCH] Remove notify in speedstep_set_state [2/2] Bruno Ducrot
2004-06-10 19:35             ` [PATCH] security fix for speedstep-smi Bruno Ducrot
2004-06-10 19:44             ` [PATCH] 2.6.5 speedstep on P4Ms Bruno Ducrot
2004-06-10 20:04             ` [PATCH] replace for_each_cpu with for_each_cpu_mask (was Re: [PATCH] 2.6.5 speedstep on P4Ms) Bruno Ducrot
2004-06-10 21:38               ` Dave Jones
2004-06-11  9:55                 ` Bruno Ducrot
  -- strict thread matches above, loose matches on Subject: below --
2004-06-11  0:21 [PATCH] 2.6.5 speedstep on P4Ms Christian Hoelbling
2004-06-11  0:30 Christian Hoelbling

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=20040610083038.GA18693@dominikbrodowski.de \
    --to=linux@dominikbrodowski.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=ducrot@poupinou.org \
    --cc=holbling@cpt.univ-mrs.fr \
    /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