Lines Matching refs:stacktrace
20 event format fields (or stacktrace) and a set of running totals
38 Keys can be any field, or the special string 'stacktrace', which
39 will use the event's kernel stacktrace as the key. The keywords
57 'stacktrace' fields and can therefore be combined using those
540 value 'stacktrace' for the key parameter::
542 # echo 'hist:keys=stacktrace:values=bytes_req,bytes_alloc:sort=bytes_alloc' > \
554 …# trigger info: hist:keys=stacktrace:vals=bytes_req,bytes_alloc:sort=bytes_alloc:size=2048 [active]
556 { stacktrace:
574 { stacktrace:
589 { stacktrace:
601 { stacktrace:
609 { stacktrace:
618 { stacktrace:
629 { stacktrace:
1016 First we set up an initially paused stacktrace trigger on the
1019 # echo 'hist:key=stacktrace:vals=len:pause' > \
1028 hash table keyed on stacktrace::
1053 # trigger info: hist:keys=stacktrace:vals=len:sort=hitcount:size=2048 [paused]
1055 { stacktrace:
1072 { stacktrace:
1090 { stacktrace:
1108 { stacktrace:
1135 # echo 'hist:key=stacktrace:vals=len:clear' >> \
1142 # trigger info: hist:keys=stacktrace:vals=len:sort=hitcount:size=2048 [paused]
1478 other than 'hitcount' and 'stacktrace'. These commands create a
1481 # echo 'hist:name=bar:key=stacktrace:val=hitcount' > \
1483 # echo 'hist:name=bar:key=stacktrace:val=hitcount' > \
1494 # trigger info: hist:name=bar:keys=stacktrace:vals=hitcount:sort=hitcount:size=2048 [active]
1497 { stacktrace:
1503 { stacktrace:
1521 { stacktrace:
1536 { stacktrace:
1554 { stacktrace:
1572 { stacktrace:
1590 { stacktrace: