From: Mulyadi Santosa
Fixing "profile" kernel parameter:
- adding "kvm" parameter description
- a bit more verbose explanation of "schedule"/"sleep" param
- explicitly tells that CPU profiling is the default mode
if none is mentioned.
Done against vanilla 2.6.23.13
PS: I am not subscribed to linux-kernel@vger, so please kindly Cc:
your reply to my e-mail address.
Signed-off-by: Mulyadi Santosa <mulyadi.santosa@gmail.com>
---
Documentation/kernel-parameters.txt | 19 +++++++++++++------
1 file changed, 13 insertions(+), 6 deletions(-)
--- linux-2.6.23.13/Documentation/kernel-parameters.txt.bak 2008-01-10
00:18:17.000000000 +0700
+++ linux-2.6.23.13/Documentation/kernel-parameters.txt 2008-01-25
22:49:37.000000000 +0700
@@ -1391,12 +1391,19 @@ and is between 256 and 4096 characters.
Format: <bool> (1/Y/y=enable, 0/N/n=disable)
profile= [KNL] Enable kernel profiling via /proc/profile
- Format: [schedule,]<number>
- Param: "schedule" - profile schedule points.
- Param: <number> - step/bucket size as a power of 2 for
- statistical time based profiling.
- Param: "sleep" - profile D-state sleeping (millisecs)
-
+ Format: [schedule/sleep/kvm,]<number>
+ First param is one of these (they can't be combined!):
+ Param: "schedule" - profile schedule() call.
+ Param: "sleep" - profile where a task sleeps (millisecs).
+ Param: "kvm" - profile KVM exit call.
+
+ If first param is omitted then cpu profiling mode
+ is effectively applied. In this mode, profiling is
+ done in tick handler.
+
+ Second param: <number> - step/bucket size as a power
+ of 2 for statistical time based profiling.
+
processor.max_cstate= [HW,ACPI]
Limit processor to maximum C-state
max_cstate=9 overrides any DMI blacklist limit.
--
