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] firewire/amdtp-stream.c?h=nds-private-remove'>logtreecommitdiff
e='8b1b41ee74f9712c355d66dc105bbea663ae0afd'/>
AgeCommit message (Expand)AuthorFilesLines
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-02-06 19:36:04 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-02-06 19:36:04 -0800
commit8b1b41ee74f9712c355d66dc105bbea663ae0afd (patch)
tree4c3f410f3cb01c7b00b474e376a60f27a7ff99a8 /drivers/usb/dwc3/gadget.c
parentf7d6040aa45df6ffd9e891114125dc919f18b96b (diff)
parentbfb34527a32a1a576d9bfb7026d3ab0369a6cd60 (diff)
Merge branch 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
Pull libnvdimm fixes from Dan Williams: "None of these are showstoppers for 4.10 and could wait for 4.11 merge window, but they are low enough risk for this late in the cycle and the fixes have waiting users . They have received a build success notification from the 0day robot, pass the latest ndctl unit tests, and appeared in next: - Fix a crash that can result when SIGINT is sent to a process that is awaiting completion of an address range scrub command. We were not properly cleaning up the workqueue after wait_event_interruptible(). - Fix a memory hotplug failure condition that results from not reserving enough space out of persistent memory for the memmap. By default we align to 2M allocations that the memory hotplug code assumes, but if the administrator specifies a non-default 4K-alignment then we can fail to correctly size the reservation. - A one line fix to improve the predictability of libnvdimm block device names. A common operation is to reconfigure /dev/pmem0 into a different mode. For example, a reconfiguration might set a new mode that reserves some of the capacity for a struct page memmap array. It surprises users if the device name changes to "/dev/pmem0.1" after the mode change and then back to /dev/pmem0 after a reboot. - Add 'const' to some function pointer tables" * 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm: libnvdimm, pfn: fix memmap reservation size versus 4K alignment acpi, nfit: fix acpi_nfit_flush_probe() crash libnvdimm, namespace: do not delete namespace-id 0 nvdimm: constify device_type structures
Diffstat (limited to 'drivers/usb/dwc3/gadget.c')