diff options
| author | Lin Feng <[email protected]> | 2019-05-14 22:42:31 +0000 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2019-05-15 02:52:49 +0000 |
| commit | 0cc75888dad112395df0ac755915ceb79811831c (patch) | |
| tree | 96f90ffd7e02be7b99619dd7ca2d4d1bd338c5fb /lib/bitmap.c | |
| parent | kernel/notifier.c: double register detection (diff) | |
| download | kernel-0cc75888dad112395df0ac755915ceb79811831c.tar.gz kernel-0cc75888dad112395df0ac755915ceb79811831c.zip | |
kernel/latencytop.c: remove unnecessary checks for latencytop_enabled
1. In latencytop source codes, we only have such calling chain:
account_scheduler_latency(struct task_struct *task, int usecs, int inter)
{
if (unlikely(latencytop_enabled)) /* the outtermost check */
__account_scheduler_latency(task, usecs, inter);
}
__account_scheduler_latency
account_global_scheduler_latency
if (!latencytop_enabled)
So, the inner check for latencytop_enabled is not necessary at all.
2. In clear_all_latency_tracing and now is called
clear_tsk_latency_tracing the check for latencytop_enabled is redundant
and buggy to some extent.
We have no reason to refuse clearing the /proc/$pid/latency if
latencytop_enabled is set to 0, considering that if we use latencytop
manually by echo 0 > /proc/sys/kernel/latencytop, then we want to clear
/proc/$pid/latency and failed.
Also we don't have such check in brother function
clear_global_latency_tracing.
Notes: These changes are only visible to users who set
CONFIG_LATENCYTOP and won't change user tool latencytop's behavior.
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Lin Feng <[email protected]>
Cc: Alexey Dobriyan <[email protected]>
Cc: Fabian Frederick <[email protected]>
Cc: Arjan van de Ven <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'lib/bitmap.c')
0 files changed, 0 insertions, 0 deletions
