All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/2] Add a passive cooling trip point if the firmware doesn't define one
Date: Thu, 15 May 2008 00:01:15 +0100	[thread overview]
Message-ID: <20080514230115.GA11960@srcf.ucam.org> (raw)
In-Reply-To: <200805141137.22341.lenb@kernel.org>

On Wed, May 14, 2008 at 11:37:22AM -0400, Len Brown wrote:

> No.
> ACPI thermal zones with no passive trip points can be used
> to simply report interesting temperature events to user-space
> (via the spiffy new generic thermal class).
> User-space then invokes corrective action -- which may be
> something _other_ than throttling the CPU.

If user space wants to decouple ACPI from the generic thermal model, 
then it can do so by using the mode file in the sysfs node. That doesn't 
change.

> > Menlow has a more complex thermal model than machines we've seen up to 
> > now, but I was under the impression that this was to be handled by the 
> > new generic thermal class rather than the existing ACPI code. I don't 
> > see this patch as being in conflict with supporting that.
> 
> No.
> It is a direct conflict.
> 
> Say the thermal zone is related to the communications chip.
> If we create a phantom passive trip point for that zone
> and throttle the CPU when it fires, we're shooting ourselves
> in the head (when we should be poking ourselves in the ear, or some such:-)

As I said, if userspace is managing the thermal envelope then it has to 
indicate this by writing a value into sysfs (see the get_mode and 
set_mode calls in the thermal_zone_device_ops structure). If that's 
done then it indicates to the kernel that it should leave control up to 
the userspace application. acpi_thermal_check will then return without 
handling the trip points (including the critical one, which I'm not sure 
sounds like a good idea...)

As a result, this patch doesn't conflict with the userspace thermal 
management at all. The moment the userspace policy daemon starts up 
it'll disable the code that would fire on the passive trip point. If 
you're not using a userspace policy daemon, then the only hardware that 
can be used to drop the temperature is the processor. Which is what this 
patch does.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2008-05-14 23:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  1:00 [PATCH] Fix polling policy in the absence of _TZP Matthew Garrett
2008-05-14  1:03 ` [PATCH 1/2] Add a list of processor objects to the ACPI core Matthew Garrett
2008-05-14  1:08   ` [PATCH 2/2] Add a passive cooling trip point if the firmware doesn't define one Matthew Garrett
2008-05-14  3:30     ` Len Brown
2008-05-14  9:33       ` Matthew Garrett
2008-05-14 15:37         ` Len Brown
2008-05-14 23:01           ` Matthew Garrett [this message]
2008-05-15  0:55         ` Zhang Rui
2008-05-15  1:04           ` Matthew Garrett
     [not found]             ` <1210814699.2929.10.camel@rzhang-crestline.sh.intel.com>
     [not found]               ` <20080515015831.GA14829@srcf.ucam.org>
2008-05-15  2:15                 ` Zhang Rui
2008-05-15  2:24                   ` Matthew Garrett
2008-05-15  3:06                     ` Zhang Rui
2008-05-15 11:40                       ` Matthew Garrett
2008-05-15 11:47       ` Andi Kleen
2008-05-15 12:02         ` Matthew Garrett
2008-05-14  3:19 ` [PATCH] Fix polling policy in the absence of _TZP Len Brown
2008-05-14 10:14   ` Matthew Garrett

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=20080514230115.GA11960@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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 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.