Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1366091

Re: [PATCH v16 22/23] tracing: Add hist trigger 'log2' modifier

Show all headers | View raw

Hi,

On 03/03/2016 07:55 PM, Tom Zanussi wrote:
> When using '.log2' modifier, the output looks like:
> 
>   # echo 'hist:key=bytes_req.log2' > kmalloc/trigger
>   # cat kmalloc/hist
> 
>   { bytes_req: ~ 2^12 } hitcount:          1
>   { bytes_req: ~ 2^11 } hitcount:          1
>   { bytes_req: ~ 2^9  } hitcount:          2
>   { bytes_req: ~ 2^6  } hitcount:          3
>   { bytes_req: ~ 2^3  } hitcount:         13
>   { bytes_req: ~ 2^5  } hitcount:         19
>   { bytes_req: ~ 2^8  } hitcount:         49
>   { bytes_req: ~ 2^7  } hitcount:         57
>   { bytes_req: ~ 2^4  } hitcount:         74


I found a small inconsistency. My command line is

  echo 'hist:key=latency.log2:sort=latency' > /sys/kernel/debug/tracing/events/test/latency_complete/trigger

When looking at the output of 'hist' you see that the 
'sort=' is not what I provided.

cat /sys/kernel/debug/tracing/events/test/latency_complete/hist
# event histogram
#
# trigger info: hist:keys=latency.log2:vals=hitcount:sort=latency.log2:size=2048 [active]
#
#

This is not terrible important. 

cheers,
daniel

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH v16 22/23] tracing: Add hist trigger 'log2' modifier Daniel Wagner <wagi@monom.org> - 2016-03-29 12:10 +0200
  Re: [PATCH v16 22/23] tracing: Add hist trigger 'log2' modifier Namhyung Kim <namhyung@kernel.org> - 2016-03-29 17:20 +0200
    Re: [PATCH v16 22/23] tracing: Add hist trigger 'log2' modifier Daniel Wagner <wagi@monom.org> - 2016-03-31 07:10 +0200

csiph-web