cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	mzahor@dtech.sk, Dominik Brodowski <linux@dominikbrodowski.net>,
	cpufreq <cpufreq@lists.linux.org.uk>
Subject: Re: [PATCH] Remove p4_clockmode driver
Date: Mon, 26 May 2008 14:56:54 +0200	[thread overview]
Message-ID: <1211806614.29901.212.camel@queen.suse.de> (raw)
In-Reply-To: <20080526120507.GA23310@srcf.ucam.org>

On Mon, 2008-05-26 at 13:05 +0100, Matthew Garrett wrote:
> On Sun, May 25, 2008 at 05:39:31PM +0200, Thomas Renninger wrote:
> 
> > Could you explain this in two easy sentences again, why this should not
> > use the throttling interface?
> 
> Because it involves rewriting code for purely aesthetic benefit. I agree 
> that, in an ideal world, p4-clockmod would integrate into the throttling 
> system. But unless someone wants to rewrite it, that doesn't look 
> likely...
Yes, I should add a p4-clockmod filter and move all upcoming issues on
the cpufreq list automatically to the trash...
> 
> > (former /proc/acpi/processor/*/throttling, now somewhere located in
> > sysfs. Also used for passive cooling if no cpufreq is available).
> > Throttling is what this driver is doing and with which it will interfere
> > and slow down the machine to be closed to unresponsive if both
> > (throttling and cpufreq interface) are using it?
> 
> The ACPI throttling interface will only be used if the minimum cpufreq 
> state has already been reached.
Yes and this is correct.
If there should really be a machine out there which can do real cpufreq
scaling and the p4-clockmod driver still works, real cpufreq scaling
should be preferred.
> Users really shouldn't play with the 
> throttling interface themselves, given its lack of useful functionality.
Right, this also applies for p4-clockmod. Therefore, if at all, this
should get moved to throttling. There it will be used for what it is
designed for: passive cooling to avoid critical temperatures. This is
done automatically through the trip points interface without the need of
user interaction (Yes, BIOSes do not define a passive trip point...,
this should hopefully be possible via userspace soon).

To be honest I do not care that much about removing this one. IMO things
should be cleaned up from time to time.
While ThinkPads, Acer, Dell seem to run quite hot currently with
powersaving capble CPUs, or cpufreq is broken or buggy on some, I am
tired discussing about p4-clockmod.
People waste time and file bugs on such unimportant things like
powersaving on a P4 and writing all this down and try to convince people
that p4-clockmod is not worth it is also not worth it. At least state
that this driver should not be used in distributions to not get
complains about this one any more or just remove it..., Dmitry can
compile it in for himself to save 2 degree and Pavel or whoever it was
with the broken battery... I mean does this still work, I expect the
battery is really broken now and you should be able to use this machine
on full performance again. As said p4-clockmod does only save if CPU is
utilized, but then you do not want throttling, only for critical
temperature reasons or broken batteries.

   Thomas

  reply	other threads:[~2008-05-26 12:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-03 19:47 [PATCH] Remove p4_clockmode driver Thomas Renninger
2008-05-11 16:19 ` Dave Jones
2008-05-15 10:55   ` Dominik Brodowski
2008-05-16 18:32   ` Pallipadi, Venkatesh
2008-05-22  4:01   ` Dmitry Torokhov
2008-05-23 11:21     ` Thomas Renninger
2008-05-23 12:55       ` Dmitry Torokhov
2008-05-23 15:19         ` Thomas Renninger
2008-05-23 15:54           ` Dmitry Torokhov
2008-05-23 16:16             ` Thomas Renninger
2008-05-23 17:40               ` Dmitry Torokhov
2008-05-24 11:03                 ` Dominik Brodowski
2008-05-25 15:39                   ` Thomas Renninger
2008-05-26 12:05                     ` Matthew Garrett
2008-05-26 12:56                       ` Thomas Renninger [this message]
2008-05-12 22:30 ` Cesar Eduardo Barros

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=1211806614.29901.212.camel@queen.suse.de \
    --to=trenn@suse.de \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux@dominikbrodowski.net \
    --cc=mjg59@srcf.ucam.org \
    --cc=mzahor@dtech.sk \
    /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