On Tue, Jul 21, 2015 at 11:45:01PM +0900, Namhyung Kim wrote:
SNIP
> > >
> > > [jolsa@krava perf]$ ./perf record -e 'cpu/instructions,period=20000/' -c
> > > 1000 sleep 1 [ perf record: Woken up 1 times to write data ] /proc/kcore
> > > requires CAP_SYS_RAWIO capability to access.
> > > [ perf record: Captured and wrote 0.015 MB perf.data (35 samples) ]
> > > [jolsa@krava perf]$ ./perf evlist -vv
> > > cpu/instructions,period=20000/: type: 4, size: 112, config: 0xc0,
> > > { sample_period, sample_freq }: 20000
> > >
> >
> > So you are going to change current behavior?
> > The current behavior is "global opts setting" > "per_event settring" >
> > default
> > You are going to change it to "per_event settring" > "global opts setting" >
> > Default. Right?
>
> Hmm.. I agree that changing current behavior is not good. But I think
> it makes more sense to prefer per-event settings over global settings
> in general.
hum right.. but it's just period ATM that will be affected..
I'd risk it, since I dont think maybe people actualy used it ;-)
together with time term, which wasn't possible to change before
anyway, so there should be no problem
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
