From: Dave Jones <davej@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: colin.michael@o2online.de, linux-kernel@vger.kernel.org
Subject: Re: [patch] enable userspace cpu core voltage control with acpi-cpufreq
Date: Mon, 3 Sep 2007 11:24:57 -0400 [thread overview]
Message-ID: <20070903152457.GC21586@redhat.com> (raw)
In-Reply-To: <p738x7oaugi.fsf@bingen.suse.de>
On Mon, Sep 03, 2007 at 12:56:13PM +0200, Andi Kleen wrote:
> <colin.michael@o2online.de> writes:
>
> > i want to make a patch known that provides a userspace interface to control the core voltage of a computer processor(s).
>
> That would be essentially linux supported undervolting which
> for stability is as bad as overclocking. The problem is that
> such games tend to generate weird kernel crashes and then
> chew up development issues when kernel hackers have to chase
> ghost bugs. I don't think we should support it. Developer
> time is too precious.
Seconded. Exactly the same reasons I've refused to merge patches
into cpufreq to allow arbitrary tables to override BIOS tables.
Or patches to remove boundary checks. Even when correctly
implemented, this stuff can be fragile as hell, so introducing
more things that cast doubt over its stability isn't something
I'm keen on at all.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-09-03 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 14:41 [patch] enable userspace cpu core voltage control with acpi-cpufreq colin.michael
2007-09-02 22:07 ` Arjan van de Ven
2007-09-03 10:56 ` Andi Kleen
2007-09-03 15:24 ` Dave Jones [this message]
2007-09-09 14:48 ` Pavel Machek
2007-09-10 21:04 ` [patch] enable userspace cpu core voltage control withacpi-cpufreq Pallipadi, Venkatesh
2007-09-04 11:49 ` [patch] enable userspace cpu core voltage control with acpi-cpufreq Len Brown
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=20070903152457.GC21586@redhat.com \
--to=davej@redhat.com \
--cc=andi@firstfloor.org \
--cc=colin.michael@o2online.de \
--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