Re: [RFC 00/79] perf tools: Initial libperf separation

2019-08-05 Thread Alexey Budankov
On 21.07.2019 14:23, Jiri Olsa wrote: > hi, > we have long term goal to separate some of the perf functionality > into library. This patchset is initial effort on separating some > of the interface. > > Currently only the basic counting interface is exported, it allows > to: > - create cpu/thr

Re: [RFC 00/79] perf tools: Initial libperf separation

2019-07-25 Thread Arnaldo Carvalho de Melo
Em Sun, Jul 21, 2019 at 01:23:47PM +0200, Jiri Olsa escreveu: > hi, > we have long term goal to separate some of the perf functionality > into library. This patchset is initial effort on separating some > of the interface. > > Currently only the basic counting interface is exported, it allows > to

Re: [RFC 00/79] perf tools: Initial libperf separation

2019-07-24 Thread Song Liu
> On Jul 24, 2019, at 6:50 AM, Arnaldo Carvalho de Melo > wrote: > > Em Wed, Jul 24, 2019 at 07:42:50AM +, Song Liu escreveu: >>> On Jul 21, 2019, at 4:23 AM, Jiri Olsa wrote: > >>> we have long term goal to separate some of the perf functionality >>> into library. This patchset is init

Re: [RFC 00/79] perf tools: Initial libperf separation

2019-07-24 Thread Arnaldo Carvalho de Melo
Em Wed, Jul 24, 2019 at 07:42:50AM +, Song Liu escreveu: > > On Jul 21, 2019, at 4:23 AM, Jiri Olsa wrote: > > we have long term goal to separate some of the perf functionality > > into library. This patchset is initial effort on separating some > > of the interface. > > Currently only the b

Re: [RFC 00/79] perf tools: Initial libperf separation

2019-07-24 Thread Jiri Olsa
On Mon, Jul 22, 2019 at 09:23:36AM -0700, Ian Rogers wrote: > This is really helpful and thank you for taking the initiative! I've > no real feedback other than to offer support. > We've been looking in this direction to avoid memory overhead in: > https://github.com/google/perf_data_converter > So

Re: [RFC 00/79] perf tools: Initial libperf separation

2019-07-24 Thread Song Liu
> On Jul 24, 2019, at 1:33 AM, Jiri Olsa wrote: > > On Wed, Jul 24, 2019 at 07:42:50AM +, Song Liu wrote: >> Hi Jiri, >> >>> On Jul 21, 2019, at 4:23 AM, Jiri Olsa wrote: >>> >>> hi, >>> we have long term goal to separate some of the perf functionality >>> into library. This patchset is

Re: [RFC 00/79] perf tools: Initial libperf separation

2019-07-24 Thread Jiri Olsa
On Wed, Jul 24, 2019 at 07:42:50AM +, Song Liu wrote: > Hi Jiri, > > > On Jul 21, 2019, at 4:23 AM, Jiri Olsa wrote: > > > > hi, > > we have long term goal to separate some of the perf functionality > > into library. This patchset is initial effort on separating some > > of the interface. >

Re: [RFC 00/79] perf tools: Initial libperf separation

2019-07-24 Thread Song Liu
Hi Jiri, > On Jul 21, 2019, at 4:23 AM, Jiri Olsa wrote: > > hi, > we have long term goal to separate some of the perf functionality > into library. This patchset is initial effort on separating some > of the interface. > > Currently only the basic counting interface is exported, it allows > to

Re: [RFC 00/79] perf tools: Initial libperf separation

2019-07-22 Thread Ian Rogers
This is really helpful and thank you for taking the initiative! I've no real feedback other than to offer support. We've been looking in this direction to avoid memory overhead in: https://github.com/google/perf_data_converter Some use cases: 1) streaming protobuf rather than perf.data files, 2) us

[RFC 00/79] perf tools: Initial libperf separation

2019-07-21 Thread Jiri Olsa
hi, we have long term goal to separate some of the perf functionality into library. This patchset is initial effort on separating some of the interface. Currently only the basic counting interface is exported, it allows to: - create cpu/threads maps - create evlist/evsel objects - add evsel