| @@ -1,40 +1,40 @@ | | | @@ -1,40 +1,40 @@ |
1 | .\" $NetBSD: acpicpu.4,v 1.5 2010/08/09 16:13:21 jruoho Exp $ | | 1 | .\" $NetBSD: acpicpu.4,v 1.6 2010/08/10 02:43:50 jruoho Exp $ |
2 | .\" | | 2 | .\" |
3 | .\" Coyright (c) 2010 Jukka Ruohonen <jruohonen@iki.fi> | | 3 | .\" Coyright (c) 2010 Jukka Ruohonen <jruohonen@iki.fi> |
4 | .\" All rights reserved. | | 4 | .\" All rights reserved. |
5 | .\" | | 5 | .\" |
6 | .\" Redistribution and use in source and binary forms, with or without | | 6 | .\" Redistribution and use in source and binary forms, with or without |
7 | .\" modification, are permitted provided that the following conditions | | 7 | .\" modification, are permitted provided that the following conditions |
8 | .\" are met: | | 8 | .\" are met: |
9 | .\" 1. Redistributions of source code must retain the above copyright | | 9 | .\" 1. Redistributions of source code must retain the above copyright |
10 | .\" notice, this list of conditions and the following disclaimer. | | 10 | .\" notice, this list of conditions and the following disclaimer. |
11 | .\" 2. Neither the name of the author nor the names of any | | 11 | .\" 2. Neither the name of the author nor the names of any |
12 | .\" contributors may be used to endorse or promote products derived | | 12 | .\" contributors may be used to endorse or promote products derived |
13 | .\" from this software without specific prior written permission. | | 13 | .\" from this software without specific prior written permission. |
14 | .\" | | 14 | .\" |
15 | .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS | | 15 | .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS |
16 | .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED | | 16 | .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED |
17 | .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR | | 17 | .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR |
18 | .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS | | 18 | .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS |
19 | .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR | | 19 | .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR |
20 | .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF | | 20 | .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF |
21 | .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS | | 21 | .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS |
22 | .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN | | 22 | .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN |
23 | .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) | | 23 | .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) |
24 | .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE | | 24 | .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE |
25 | .\" POSSIBILITY OF SUCH DAMAGE. | | 25 | .\" POSSIBILITY OF SUCH DAMAGE. |
26 | .\" | | 26 | .\" |
27 | .Dd August 9, 2010 | | 27 | .Dd August 10, 2010 |
28 | .Dt ACPICPU 4 | | 28 | .Dt ACPICPU 4 |
29 | .Os | | 29 | .Os |
30 | .Sh NAME | | 30 | .Sh NAME |
31 | .Nm acpicpu | | 31 | .Nm acpicpu |
32 | .Nd ACPI CPU | | 32 | .Nd ACPI CPU |
33 | .Sh SYNOPSIS | | 33 | .Sh SYNOPSIS |
34 | .Cd "acpicpu* at acpi?" | | 34 | .Cd "acpicpu* at acpi?" |
35 | .Sh DESCRIPTION | | 35 | .Sh DESCRIPTION |
36 | The | | 36 | The |
37 | .Nm | | 37 | .Nm |
38 | device driver supports certain processor features that are | | 38 | device driver supports certain processor features that are |
39 | either only available via | | 39 | either only available via |
40 | .Tn ACPI | | 40 | .Tn ACPI |
| @@ -176,26 +176,36 @@ frequency management, | | | @@ -176,26 +176,36 @@ frequency management, |
176 | .Tn ACPI | | 176 | .Tn ACPI |
177 | provides support for Dynamic Frequency and Voltage Scaling | | 177 | provides support for Dynamic Frequency and Voltage Scaling |
178 | .Pq Tn DVFS . | | 178 | .Pq Tn DVFS . |
179 | This means that the firmware may request the implementation to | | 179 | This means that the firmware may request the implementation to |
180 | dynamically scale the presently supported maximum clock frequency. | | 180 | dynamically scale the presently supported maximum clock frequency. |
181 | For example, if | | 181 | For example, if |
182 | .Xr acpiacad 4 | | 182 | .Xr acpiacad 4 |
183 | is disconnected, the maximum available frequency may be lowered. | | 183 | is disconnected, the maximum available frequency may be lowered. |
184 | Currently the | | 184 | Currently the |
185 | .Nx | | 185 | .Nx |
186 | implementation reacts to these events by imposing the dynamic maximum, but | | 186 | implementation reacts to these events by imposing the dynamic maximum, but |
187 | .Nm | | 187 | .Nm |
188 | does not take any actions to manipulate the frequencies by itself. | | 188 | does not take any actions to manipulate the frequencies by itself. |
| | | 189 | .Ss Statistics |
| | | 190 | The |
| | | 191 | .Nm |
| | | 192 | driver uses event counters to track the times |
| | | 193 | a processor has entered a given state. |
| | | 194 | It is possible to view the statistics by using |
| | | 195 | .Xr vmstat 1 |
| | | 196 | (with the argument |
| | | 197 | .Ar -e ) . |
| | | 198 | Note that valid per-CPU data is available only for C-states. |
189 | .Sh SEE ALSO | | 199 | .Sh SEE ALSO |
190 | .Xr acpi 4 , | | 200 | .Xr acpi 4 , |
191 | .Xr cpu_idle 9 | | 201 | .Xr cpu_idle 9 |
192 | .Sh HISTORY | | 202 | .Sh HISTORY |
193 | The | | 203 | The |
194 | .Nm | | 204 | .Nm |
195 | device driver appeared in | | 205 | device driver appeared in |
196 | .Nx 6.0 . | | 206 | .Nx 6.0 . |
197 | .Sh AUTHORS | | 207 | .Sh AUTHORS |
198 | .An Jukka Ruohonen | | 208 | .An Jukka Ruohonen |
199 | .Aq jruohonen@iki.fi | | 209 | .Aq jruohonen@iki.fi |
200 | .Sh CAVEATS | | 210 | .Sh CAVEATS |
201 | The | | 211 | The |
| @@ -227,21 +237,14 @@ Neither processor thermal control (see | | | @@ -227,21 +237,14 @@ Neither processor thermal control (see |
227 | .Xr acpitz 4 ) | | 237 | .Xr acpitz 4 ) |
228 | nor | | 238 | nor |
229 | .Dq throttling | | 239 | .Dq throttling |
230 | are currently supported. | | 240 | are currently supported. |
231 | .It | | 241 | .It |
232 | There is currently neither a well-defined, machine-independent | | 242 | There is currently neither a well-defined, machine-independent |
233 | .Tn API | | 243 | .Tn API |
234 | for processor performance management nor a | | 244 | for processor performance management nor a |
235 | .Dq governor | | 245 | .Dq governor |
236 | for different policies. | | 246 | for different policies. |
237 | It is only possible to control the | | 247 | It is only possible to control the |
238 | .Tn CPU | | 248 | .Tn CPU |
239 | frequencies from userland. | | 249 | frequencies from userland. |
240 | .It | | | |
241 | There are currently no proper ways to export | | | |
242 | statistical and other information from | | | |
243 | .Nm . | | | |
244 | This applies to | | | |
245 | .Tn ACPI | | | |
246 | generally. | | | |
247 | .El | | 250 | .El |