perf-kmem(1) ============ NAME ---- perf-kmem - Tool to trace/measure kernel memory properties SYNOPSIS -------- [verse] 'perf kmem' {record|stat} [] DESCRIPTION ----------- There are two variants of perf kmem: 'perf kmem record ' to record the kmem events of an arbitrary workload. 'perf kmem stat' to report kernel memory statistics. OPTIONS ------- -i :: --input=:: Select the input file (default: perf.data unless stdin is a fifo) -v:: --verbose:: Be more verbose. (show symbol address, etc) --caller:: Show per-callsite statistics --alloc:: Show per-allocation statistics -s :: --sort=:: Sort the output (default: 'frag,hit,bytes' for slab and 'bytes,hit' for page). Available sort keys are 'ptr, callsite, bytes, hit, pingpong, frag' for slab and 'page, callsite, bytes, hit, order, migtype, gfp' for page. This option should be preceded by one of the mode selection options - i.e. --slab, --page, --alloc and/or --caller. -l :: --line=:: Print n lines only --raw-ip:: Print raw ip instead of symbol --slab:: Analyze SLAB allocator events. --page:: Analyze page allocator events --live:: Show live page stat. The perf kmem shows total allocation stat by default, but this option shows live (currently allocated) pages instead. (This option works with --page option only) --time:: Only analyze samples within given time window: ,. Times have the format seconds.microseconds. If start is not given (i.e., time string is ',x.y') then analysis starts at the beginning of the file. If stop time is not given (i.e, time string is 'x.y,') then analysis goes to end of file. SEE ALSO -------- linkperf:perf-record[1] logtreecommitdiff
diff options
context:
space:
mode:
authorColin Ian King <colin.king@canonical.com>2017-01-11 15:36:20 +0000
committerMark Brown <broonie@kernel.org>2017-01-18 16:32:44 +0000
commitb98acbff9a05b371c5f0ca6e44a3af8ce9274379 (patch)
treed6835885f859a456e62ce93621041138d6a54f9b /drivers/usb/musb/musb_am335x.c
parentd00b74613fb18dfd0a5aa99270ee2e72d5c808d7 (diff)
regulator: twl6030: fix range comparison, allowing vsel = 59
The range min_uV > 1350000 && min_uV <= 150000 is never reachable because of a typo in the previous range check and hence vsel = 59 is never reached. Fix the previous range check to enable the vsel = 59 setting. Fixes CoverityScan CID#728454 ("Logially dead code") Signed-off-by: Colin Ian King <colin.king@canonical.com> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/usb/musb/musb_am335x.c')