From: Pavel Machek <pavel@suse.cz>
To: linux@brodo.de
Cc: acpi-devel@lists.sourceforge.net, andrew.grover@intel.com,
cpufreq@www.linux.org.uk
Subject: Re: [ACPI] [PATCHES] ACPI Processor update [idle, throttling, thermal, cpufreq]
Date: Wed, 10 Sep 2003 02:00:41 +0200 [thread overview]
Message-ID: <20030910000041.GC217@elf.ucw.cz> (raw)
In-Reply-To: <20030909232916.GA9561@brodo.de>
Hi!
> > > > http://www.brodo.de/cpufreq_tmp/acpi-2.6.0-test4-processor_thermal_throttling
> > > > > Move throttling into its own submodule, and register it with the new
> > > > > passive cooling module. Also, the now-useless "limit" interface is
> > > > > removed.
> > > > >
> > > >
> > > > Actually I liked to be able to echo 0:7 > limit and conserve battery/
> > > > make sure machine does not overheat with it...
> > >
> > > echo 7 > throttling should do the same thing.
> >
> > Will not first change in thermal system unthrottle it for me, behind
> > my back?
>
> Well yes, it might, if the temperature had been higher than the passive
> cooling trip point. If you want me to, I'll change the behaviour so that the
> /proc/acpi/.../throttling input is consistent (minimum limit) until the user
> choses a different throttling level.
Yes I guess that would make sense.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: linux-JhLEnvuH02M@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
cpufreq-1walMZg8u8rXmaaqVzeoHQ@public.gmane.org
Subject: Re: [ACPI] [PATCHES] ACPI Processor update [idle, throttling, thermal, cpufreq]
Date: Wed, 10 Sep 2003 02:00:41 +0200 [thread overview]
Message-ID: <20030910000041.GC217@elf.ucw.cz> (raw)
In-Reply-To: <20030909232916.GA9561-JhLEnvuH02M@public.gmane.org>
Hi!
> > > > http://www.brodo.de/cpufreq_tmp/acpi-2.6.0-test4-processor_thermal_throttling
> > > > > Move throttling into its own submodule, and register it with the new
> > > > > passive cooling module. Also, the now-useless "limit" interface is
> > > > > removed.
> > > > >
> > > >
> > > > Actually I liked to be able to echo 0:7 > limit and conserve battery/
> > > > make sure machine does not overheat with it...
> > >
> > > echo 7 > throttling should do the same thing.
> >
> > Will not first change in thermal system unthrottle it for me, behind
> > my back?
>
> Well yes, it might, if the temperature had been higher than the passive
> cooling trip point. If you want me to, I'll change the behaviour so that the
> /proc/acpi/.../throttling input is consistent (minimum limit) until the user
> choses a different throttling level.
Yes I guess that would make sense.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-09-10 0:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 22:24 [PATCHES] ACPI Processor update [idle,throttling,thermal,cpufreq] Dominik Brodowski
2003-09-04 22:24 ` Dominik Brodowski
2003-09-05 5:23 ` [ACPI] [PATCHES] ACPI Processor update [idle, throttling, thermal, cpufreq] Dmitry Torokhov
2003-09-05 5:23 ` Dmitry Torokhov
2003-09-05 6:52 ` Dominik Brodowski
2003-09-05 6:52 ` Dominik Brodowski
2003-09-08 13:29 ` Pavel Machek
2003-09-08 13:29 ` Pavel Machek
2003-09-09 17:21 ` linux
2003-09-09 17:21 ` linux-JhLEnvuH02M
2003-09-09 23:13 ` Pavel Machek
2003-09-09 23:13 ` Pavel Machek
2003-09-09 23:29 ` linux
2003-09-09 23:29 ` linux-JhLEnvuH02M
2003-09-10 0:00 ` Pavel Machek [this message]
2003-09-10 0:00 ` Pavel Machek
[not found] ` <20030910000041.GC217-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2003-09-10 0:17 ` [PATCH] acpi 2.6: consistent user-forced throttling (9/8) [Was: Re: [PATCHES] ACPI Processor update [idle, throttling, thermal, cpufreq]] linux-JhLEnvuH02M
[not found] ` <20030910001716.GA10324-JhLEnvuH02M@public.gmane.org>
2003-09-10 10:54 ` Nils Faerber
[not found] ` <1063191264.23733.1320.camel-65LrUGLyukAb1SvskN2V4Q@public.gmane.org>
2003-09-10 12:53 ` linux-JhLEnvuH02M
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=20030910000041.GC217@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=andrew.grover@intel.com \
--cc=cpufreq@www.linux.org.uk \
--cc=linux@brodo.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.