mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: running the kernel without hal= how safe with the cpufreq
Date: Sat, 23 May 2009 14:08:30 -0700	[thread overview]
Message-ID: <20090523140830.5bff23c3@infradead.org> (raw)
In-Reply-To: <dd18b0c30905231129j7ad812e9sf3eee89864b03fb8@mail.gmail.com>

On Sat, 23 May 2009 11:29:29 -0700
Justin Mattock <justinmattock@gmail.com> wrote:

> I'm in the process of building a system
> minus hal(since udev 142 explains itself
> in the README),
> Anyways I normally just have
> "ondemand" compiled as the main
> cpufreq module, and have no powermgnt or cpufreq
> userspace tool except or was hal.
> should I be concerned
> without having hal due to things like this in
> ps auxZ

if you use ondemand you don't need anything else; the defaults
are good and in fact very very few people (if anyone) should ever
change the tunables (they're more aimed for the ondemand developers).

Any application that touches these tunables is basically broken ;)

In addition, you should always be safe against hardware breaking,
as long as you don't do things like poke chipset registers to disable
SMM etc, there is thermal protection build into the system.
First it will automatically slow down the CPU (a lot), and if that is
not sufficient/fast enough, the system will shut down before it lets
itself be damaged.



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2009-05-23 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-23 18:29 Justin Mattock
2009-05-23 21:08 ` Arjan van de Ven [this message]
2009-05-23 21:49   ` Justin Mattock

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=20090523140830.5bff23c3@infradead.org \
    --to=arjan@infradead.org \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®