Em Wed, Apr 22, 2015 at 04:08:50PM +0200, Jiri Olsa escreveu:
> On Mon, Apr 20, 2015 at 05:38:52PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Apr 20, 2015 at 10:15:39PM +0200, Jiri Olsa escreveu:
> > > On Mon, Apr 20, 2015 at 05:09:36PM -0300, Arnaldo Carvalho de Melo wrote:
> > > > Which
On Mon, Apr 20, 2015 at 05:38:52PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Apr 20, 2015 at 10:15:39PM +0200, Jiri Olsa escreveu:
> > On Mon, Apr 20, 2015 at 05:09:36PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Sat, Apr 18, 2015 at 10:42:58PM +0200, Jiri Olsa escreveu:
> > > So, do
Em Wed, Apr 22, 2015 at 04:08:50PM +0200, Jiri Olsa escreveu:
On Mon, Apr 20, 2015 at 05:38:52PM -0300, Arnaldo Carvalho de Melo wrote:
Em Mon, Apr 20, 2015 at 10:15:39PM +0200, Jiri Olsa escreveu:
On Mon, Apr 20, 2015 at 05:09:36PM -0300, Arnaldo Carvalho de Melo wrote:
Which is nice,
On Mon, Apr 20, 2015 at 05:38:52PM -0300, Arnaldo Carvalho de Melo wrote:
Em Mon, Apr 20, 2015 at 10:15:39PM +0200, Jiri Olsa escreveu:
On Mon, Apr 20, 2015 at 05:09:36PM -0300, Arnaldo Carvalho de Melo wrote:
Em Sat, Apr 18, 2015 at 10:42:58PM +0200, Jiri Olsa escreveu:
So, do you want
Em Mon, Apr 20, 2015 at 10:15:39PM +0200, Jiri Olsa escreveu:
> On Mon, Apr 20, 2015 at 05:09:36PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Sat, Apr 18, 2015 at 10:42:58PM +0200, Jiri Olsa escreveu:
> > So, do you want me to apply this series and you work on top of it or
> > should I wait for
On Mon, Apr 20, 2015 at 05:09:36PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Sat, Apr 18, 2015 at 10:42:58PM +0200, Jiri Olsa escreveu:
> > On Sat, Apr 18, 2015 at 07:39:27PM +0200, Ingo Molnar wrote:
> > > So since we now know exactly what's going on, we might want to drop
> > > the 'invalid
Em Sat, Apr 18, 2015 at 10:42:58PM +0200, Jiri Olsa escreveu:
> On Sat, Apr 18, 2015 at 07:39:27PM +0200, Ingo Molnar wrote:
> > So since we now know exactly what's going on, we might want to drop
> > the 'invalid or unsupported event' language as well, and make it
> > specific:
> >
> >$
Em Mon, Apr 20, 2015 at 10:15:39PM +0200, Jiri Olsa escreveu:
On Mon, Apr 20, 2015 at 05:09:36PM -0300, Arnaldo Carvalho de Melo wrote:
Em Sat, Apr 18, 2015 at 10:42:58PM +0200, Jiri Olsa escreveu:
So, do you want me to apply this series and you work on top of it or
should I wait for
Em Sat, Apr 18, 2015 at 10:42:58PM +0200, Jiri Olsa escreveu:
On Sat, Apr 18, 2015 at 07:39:27PM +0200, Ingo Molnar wrote:
So since we now know exactly what's going on, we might want to drop
the 'invalid or unsupported event' language as well, and make it
specific:
$ ./perf record
On Mon, Apr 20, 2015 at 05:09:36PM -0300, Arnaldo Carvalho de Melo wrote:
Em Sat, Apr 18, 2015 at 10:42:58PM +0200, Jiri Olsa escreveu:
On Sat, Apr 18, 2015 at 07:39:27PM +0200, Ingo Molnar wrote:
So since we now know exactly what's going on, we might want to drop
the 'invalid or
On Sat, Apr 18, 2015 at 07:39:27PM +0200, Ingo Molnar wrote:
>
> * Jiri Olsa wrote:
>
> > hi,
> > adding support to report error from event string parsing.
>
> Very nice!
>
> > This patchset contains support for standard parsing errors and more
> > logic to recognize tracepoint and 'pmu//'
* Jiri Olsa wrote:
> hi,
> adding support to report error from event string parsing.
Very nice!
> This patchset contains support for standard parsing errors and more
> logic to recognize tracepoint and 'pmu//' terms, like:
>
> $ perf record -e 'sched:krava' ls
> invalid or unsupported
hi,
adding support to report error from event string parsing.
This patchset contains support for standard parsing errors
and more logic to recognize tracepoint and 'pmu//' terms,
like:
$ perf record -e 'sched:krava' ls
invalid or unsupported event: 'sched:krava'
* Jiri Olsa jo...@kernel.org wrote:
hi,
adding support to report error from event string parsing.
Very nice!
This patchset contains support for standard parsing errors and more
logic to recognize tracepoint and 'pmu//' terms, like:
$ perf record -e 'sched:krava' ls
invalid or
hi,
adding support to report error from event string parsing.
This patchset contains support for standard parsing errors
and more logic to recognize tracepoint and 'pmu//' terms,
like:
$ perf record -e 'sched:krava' ls
invalid or unsupported event: 'sched:krava'
On Sat, Apr 18, 2015 at 07:39:27PM +0200, Ingo Molnar wrote:
* Jiri Olsa jo...@kernel.org wrote:
hi,
adding support to report error from event string parsing.
Very nice!
This patchset contains support for standard parsing errors and more
logic to recognize tracepoint and 'pmu//'
16 matches
Mail list logo