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
541 value 'stacktrace' for the key parameter::
543 # echo 'hist:keys=stacktrace:values=bytes_req,bytes_alloc:sort=bytes_alloc' > \
555 …# trigger info: hist:keys=stacktrace:vals=bytes_req,bytes_alloc:sort=bytes_alloc:size=2048 [active]
557 { stacktrace:
575 { stacktrace:
590 { stacktrace:
602 { stacktrace:
610 { stacktrace:
619 { stacktrace:
630 { stacktrace:
1017 First we set up an initially paused stacktrace trigger on the
1020 # echo 'hist:key=stacktrace:vals=len:pause' > \
1029 hash table keyed on stacktrace::
1054 # trigger info: hist:keys=stacktrace:vals=len:sort=hitcount:size=2048 [paused]
1056 { stacktrace:
1073 { stacktrace:
1091 { stacktrace:
1109 { stacktrace:
1136 # echo 'hist:key=stacktrace:vals=len:clear' >> \
1143 # trigger info: hist:keys=stacktrace:vals=len:sort=hitcount:size=2048 [paused]
1479 other than 'hitcount' and 'stacktrace'. These commands create a
1482 # echo 'hist:name=bar:key=stacktrace:val=hitcount' > \
1484 # echo 'hist:name=bar:key=stacktrace:val=hitcount' > \
1495 # trigger info: hist:name=bar:keys=stacktrace:vals=hitcount:sort=hitcount:size=2048 [active]
1498 { stacktrace:
1504 { stacktrace:
1522 { stacktrace:
1537 { stacktrace:
1555 { stacktrace:
1573 { stacktrace:
1591 { stacktrace: