213
edits
Mobile/Powersaving/Wakeups/Debugging: Difference between revisions
Mobile/Powersaving/Wakeups/Debugging (view source)
Revision as of 16:42, 18 October 2010
, 18 October 2010no edit summary
No edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
* Slightly underreports when compared to powertop. The reason is that each call to a wakeup-related function (like NotifyCondVar) can potentially lead to more than 1 wakeup. In other words, powertop measures absolute wakeups, the tool measures 'logical' wakeups. The two are proportional, so lowering one will lower the other. The ratio is something like 1:1.5. | * Slightly underreports when compared to powertop. The reason is that each call to a wakeup-related function (like NotifyCondVar) can potentially lead to more than 1 wakeup. In other words, powertop measures absolute wakeups, the tool measures 'logical' wakeups. The two are proportional, so lowering one will lower the other. The ratio is something like 1:1.5. | ||
=== Old Approaches to Finding Wakeups === | |||
=== Old | |||
Another approach to finding wakeups is to add some debug prints to the relevant NSPR functions, which are PR_WaitCondVar (in nsprpub/pr/src/pthreads) and so forth, e.g. | Another approach to finding wakeups is to add some debug prints to the relevant NSPR functions, which are PR_WaitCondVar (in nsprpub/pr/src/pthreads) and so forth, e.g. | ||