How to interpret cpu_idle and cpu_frequency event's trace logged by ftrace?What does this Linux kernel trace...
How many tone holes are there actually in different orchestral woodwind instruments?
What would +1/+2/+3 items be called in game?
Why was such an unrevealing title originally chosen and then changed for some International markets?
Need a non-volatile memory IC with near unlimited read/write operations capability
How to convert diagonal matrix to rectangular matrix
Generalized Behrend version for Grothendieck-Lefschetz trace formula
What exactly is a "murder hobo"?
Intern not wearing safety equipment; how could I have handled this differently?
Four ships at the ocean with the same distance
Found and corrected a mistake on someone's else paper -- praxis?
Users forgetting to regenerate PDF before sending it
How do I explain that I don't want to maintain old projects?
How was the Shuttle loaded and unloaded from its carrier aircraft?
My previous employer committed a severe violation of the law and is also being sued by me. How do I explain the situation to future employers?
Don't the events of "Forest of the Dead" contradict the fixed point in "The Wedding of River Song"?
Was it ever illegal to name a pig "Napoleon" in France?
A sequence that changes sign finally at infinity?
What is a writing material that persists nearly forever or for a long time?
Reference request: quantifier elimination test
What does the multimeter dial do internally?
What is the problem here?(all integers are irrational proof...i think so)
What minifigure is this?
How do you move up one folder in Finder?
Is it okay to roll multiple attacks that all have advantage in one cluster?
How to interpret cpu_idle and cpu_frequency event's trace logged by ftrace?
What does this Linux kernel trace mean?Resolving executable user stack trace addresses in ftraceHow interpret kworker threads names?Trace kernel object callsHow to trace the life cycle of kernel threads by following creation and switching?How to get epoch time with trace-cmd (frontend for ftrace)?How to interpret the crash dumpFailure of getting Kernel trace logsfunctions folder in trace_stat folder of ftracePerformance reduction activating trace-functionality in kernel
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I used ftrace to trace two events, cpu_frequency and cpu_idle. I am not able to find out any documentation which states how to interpret this information. I have provided two snippets from the generated trace file below, and I need to understand how to interpret cpu_frequency & cpu_idle traced events information. I have wrote my confusion below, please answer the question and provide your own insights.
FOR CPU_Frequency:
1. What is the format of the timestamp?
2. Why there are two events for each new operating frequency point, does each of the event means that the CPU started operating at that frequency or are these entry/exit pairs?
Trace output:
# tracer: nop
#
# entries-in-buffer/entries-written: 36062/36062 #P:1
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
kworker/0:1H-27 [000] ...1 1130.362603: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.362609: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.411934: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.411947: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.532595: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.532599: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.581758: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.581768: cpu_frequency: state=300000 cpu_id=0
FOR CPU_Idle:
1. What does the state=4294967295 means here, what cpu_idle state is it?
2. Where can I get the documentation/information about what these states actually mean?
<idle>-0 [000] d..2 1960.307101: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] ...2 1960.310722: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.310741: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] ...2 1960.312114: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.312131: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] .N.2 1960.314410: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.314980: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] .N.2 1960.316077: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.316539: cpu_idle: state=3 cpu_id=0
thanks.
linux-kernel
asked May 16 '14 at 13:08
Zohaib HassanZohaib Hassan
113 bronze badges
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I used ftrace to trace two events, cpu_frequency and cpu_idle. I am not able to find out any documentation which states how to interpret this information. I have provided two snippets from the generated trace file below, and I need to understand how to interpret cpu_frequency & cpu_idle traced events information. I have wrote my confusion below, please answer the question and provide your own insights.
FOR CPU_Frequency:
1. What is the format of the timestamp?
2. Why there are two events for each new operating frequency point, does each of the event means that the CPU started operating at that frequency or are these entry/exit pairs?
Trace output:
# tracer: nop
#
# entries-in-buffer/entries-written: 36062/36062 #P:1
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
kworker/0:1H-27 [000] ...1 1130.362603: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.362609: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.411934: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.411947: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.532595: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.532599: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.581758: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.581768: cpu_frequency: state=300000 cpu_id=0
FOR CPU_Idle:
1. What does the state=4294967295 means here, what cpu_idle state is it?
2. Where can I get the documentation/information about what these states actually mean?
<idle>-0 [000] d..2 1960.307101: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] ...2 1960.310722: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.310741: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] ...2 1960.312114: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.312131: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] .N.2 1960.314410: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.314980: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] .N.2 1960.316077: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.316539: cpu_idle: state=3 cpu_id=0
thanks.
linux-kernel
asked May 16 '14 at 13:08
Zohaib HassanZohaib Hassan
113 bronze badges
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I used ftrace to trace two events, cpu_frequency and cpu_idle. I am not able to find out any documentation which states how to interpret this information. I have provided two snippets from the generated trace file below, and I need to understand how to interpret cpu_frequency & cpu_idle traced events information. I have wrote my confusion below, please answer the question and provide your own insights.
FOR CPU_Frequency:
1. What is the format of the timestamp?
2. Why there are two events for each new operating frequency point, does each of the event means that the CPU started operating at that frequency or are these entry/exit pairs?
Trace output:
# tracer: nop
#
# entries-in-buffer/entries-written: 36062/36062 #P:1
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
kworker/0:1H-27 [000] ...1 1130.362603: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.362609: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.411934: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.411947: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.532595: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.532599: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.581758: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.581768: cpu_frequency: state=300000 cpu_id=0
FOR CPU_Idle:
1. What does the state=4294967295 means here, what cpu_idle state is it?
2. Where can I get the documentation/information about what these states actually mean?
<idle>-0 [000] d..2 1960.307101: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] ...2 1960.310722: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.310741: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] ...2 1960.312114: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.312131: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] .N.2 1960.314410: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.314980: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] .N.2 1960.316077: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.316539: cpu_idle: state=3 cpu_id=0
thanks.
linux-kernel
asked May 16 '14 at 13:08
Zohaib HassanZohaib Hassan
113 bronze badges
I used ftrace to trace two events, cpu_frequency and cpu_idle. I am not able to find out any documentation which states how to interpret this information. I have provided two snippets from the generated trace file below, and I need to understand how to interpret cpu_frequency & cpu_idle traced events information. I have wrote my confusion below, please answer the question and provide your own insights.
FOR CPU_Frequency:
1. What is the format of the timestamp?
2. Why there are two events for each new operating frequency point, does each of the event means that the CPU started operating at that frequency or are these entry/exit pairs?
Trace output:
# tracer: nop
#
# entries-in-buffer/entries-written: 36062/36062 #P:1
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
kworker/0:1H-27 [000] ...1 1130.362603: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.362609: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.411934: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1130.411947: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.532595: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.532599: cpu_frequency: state=1190400 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.581758: cpu_frequency: state=300000 cpu_id=0
kworker/0:1H-27 [000] ...1 1131.581768: cpu_frequency: state=300000 cpu_id=0
FOR CPU_Idle:
1. What does the state=4294967295 means here, what cpu_idle state is it?
2. Where can I get the documentation/information about what these states actually mean?
<idle>-0 [000] d..2 1960.307101: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] ...2 1960.310722: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.310741: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] ...2 1960.312114: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.312131: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] .N.2 1960.314410: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.314980: cpu_idle: state=3 cpu_id=0
<idle>-0 [000] .N.2 1960.316077: cpu_idle: state=4294967295 cpu_id=0
<idle>-0 [000] d..2 1960.316539: cpu_idle: state=3 cpu_id=0
thanks.
linux-kernel
linux-kernel
asked May 16 '14 at 13:08
Zohaib HassanZohaib Hassan
113 bronze badges
asked May 16 '14 at 13:08
Zohaib HassanZohaib Hassan
113 bronze badges
asked May 16 '14 at 13:08
Zohaib HassanZohaib Hassan
113 bronze badges
asked May 16 '14 at 13:08
Zohaib HassanZohaib Hassan
113 bronze badges
asked May 16 '14 at 13:08
Zohaib HassanZohaib Hassan
113 bronze badges
113 bronze badges
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
For CPU_Frequency:
- The timestamp format is "secs.usecs". You can find more about this on ftrace documentation: https://www.kernel.org/doc/Documentation/trace/ftrace.txt
- I think it shows the transition delay between frequencies.
For CPU_Idle:
- '4294967295' means an exit from the current state.
- The documentation can be found here: https://www.kernel.org/doc/Documentation/trace/events-power.txt
answered May 20 '16 at 18:07
FabienFabien
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f130624%2fhow-to-interpret-cpu-idle-and-cpu-frequency-events-trace-logged-by-ftrace%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
For CPU_Frequency:
- The timestamp format is "secs.usecs". You can find more about this on ftrace documentation: https://www.kernel.org/doc/Documentation/trace/ftrace.txt
- I think it shows the transition delay between frequencies.
For CPU_Idle:
- '4294967295' means an exit from the current state.
- The documentation can be found here: https://www.kernel.org/doc/Documentation/trace/events-power.txt
answered May 20 '16 at 18:07
FabienFabien
1
add a comment |
For CPU_Frequency:
- The timestamp format is "secs.usecs". You can find more about this on ftrace documentation: https://www.kernel.org/doc/Documentation/trace/ftrace.txt
- I think it shows the transition delay between frequencies.
For CPU_Idle:
- '4294967295' means an exit from the current state.
- The documentation can be found here: https://www.kernel.org/doc/Documentation/trace/events-power.txt
answered May 20 '16 at 18:07
FabienFabien
1
add a comment |
For CPU_Frequency:
- The timestamp format is "secs.usecs". You can find more about this on ftrace documentation: https://www.kernel.org/doc/Documentation/trace/ftrace.txt
- I think it shows the transition delay between frequencies.
For CPU_Idle:
- '4294967295' means an exit from the current state.
- The documentation can be found here: https://www.kernel.org/doc/Documentation/trace/events-power.txt
answered May 20 '16 at 18:07
FabienFabien
1
For CPU_Frequency:
- The timestamp format is "secs.usecs". You can find more about this on ftrace documentation: https://www.kernel.org/doc/Documentation/trace/ftrace.txt
- I think it shows the transition delay between frequencies.
For CPU_Idle:
- '4294967295' means an exit from the current state.
- The documentation can be found here: https://www.kernel.org/doc/Documentation/trace/events-power.txt
answered May 20 '16 at 18:07
FabienFabien
1
answered May 20 '16 at 18:07
FabienFabien
1
answered May 20 '16 at 18:07
FabienFabien
1
answered May 20 '16 at 18:07
FabienFabien
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f130624%2fhow-to-interpret-cpu-idle-and-cpu-frequency-events-trace-logged-by-ftrace%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
