[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160928135747.GB7467@kernel.org>
Date: Wed, 28 Sep 2016 10:57:47 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
Cc: peterz@...radead.org, maddy@...ux.vnet.ibm.com,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v21 06/19] perf, tools: Support alias descriptions
Em Tue, Sep 27, 2016 at 11:11:16AM -0700, Sukadev Bhattiprolu escreveu:
> Arnaldo Carvalho de Melo [acme@...nel.org] wrote:
> > Em Thu, Sep 15, 2016 at 03:24:43PM -0700, Sukadev Bhattiprolu escreveu:
> > > From: Andi Kleen <ak@...ux.intel.com>
> > > Add support to print alias descriptions in perf list, which
> > > are taken from the generated event files.
> > >
> > > The sorting code is changed to put the events with descriptions
> > > at the end. The descriptions are printed as possibly multiple word
> > > wrapped lines.
> >
> > So, now I'm trying to reproduce the results below, but I couldn't find a
> > tarball with those .json files for me to use, can you provide me with
> > one?
>
> The data files are in my github, in the json-code+data-v21 branch
> starting with 23bb101. They are individual commits rather than a
> tarball though.
Ok, I'll pick one for powerpc and another for x86_64 so that I can test
it and Jiri's x-compile support.
Refresh my mind, what is the plan on these files? Are we just going to
provide pointers to where to get them from vendors, ship it in the
kernel, auto-download them as part of the build process?
At least examples that allows to build and have a new 'perf test' entry
to check them automatically seems to be in order, no?
- Arnaldo
> > https://github.com/sukadev/linux.git
> >
> > Branch Description
> > ------------------------------------------------------
> > json-code-v21 Source Code only
> > json-code+data-v21 Both code and data(for build/test/pull)
> >
>
> Sukadev
Powered by blists - more mailing lists