OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Heads up: ACPI Thermal Zone monitor

Date: Thu, 27 Apr 2006 19:40:04 -0700
From: Alan Perry <Alan dot Perry at Sun dot COM>
To: on-all at eng dot sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: Heads up: ACPI Thermal Zone monitor


With the putback of

   6363985 acpica: Metropolis SMB Alerts result in high background 
system load

Solaris Nevada now has a basic ACPI Thermal Zone monitor.

ACPI on a given system may defined one or more thermal zones.  A thermal 
zone is a temperature domain within a system.  There can be a number of 
methods (which evaluate to temperature values) and objects (which 
correspond to device lists) associated with the thermal zone, including 
the current operating temperature, significant temperatures when action 
needs to be taken (trip points) and devices associated with some of 
those trip points.  For more details on what kinds of things could be 
implemented in a system, check out the ACPI specification.

The problem reported in 6363985 was the result of an interrupt storm 
caused by the ACPI thermal zone method _TMP (the current operating 
temperature) not being evaluated in response to thermal zone events 
because there was no thermal zone monitor in Solaris.  This putback 
implements a minimal, basic thermal zone monitor.  A more sophisticated 
thermal zone monitor could be implemented in the future.

So, why the heads up?

The basic thermal zone monitor that was putback is a pseudodriver that, 
among other things, handles three types of thermal zone trip points:

_HOT - If the operating temperature exceeds the _HOT (hot) temperature, 
the operating system should initiate an orderly shutdown.

_CRT - If the operating temperature exceeds the _CRT (critical) 
temperature, the operating system should shut down the system as soon as 
possible.

_ACx - If the operating temperature exceeds one of 10 _AC (active 
cooling) temperatures, the operating system should enable the 
corresponding _ALx object and disable the corresponding _ALx object for 
the previous active cooling state.

Not all systems with ACPI implement _HOT, _CRT or _ACx methods, so the 
impact of this driver on a given system will vary.

If you have any questions, just ask.

alan perry