* Michael Ellerman wrote:
> Jiri Olsa writes:
>
> > On Wed, Aug 31, 2016 at 09:15:30AM -0700, Andi Kleen wrote:
> >> > >
> >> > > >
> >> > > > I've already made some changes in pmu-events/* to support
> >> > > > this hierarchy to see how bad the change would be.. and
> >> > > > it's not that
Jiri Olsa writes:
> On Wed, Aug 31, 2016 at 09:15:30AM -0700, Andi Kleen wrote:
>> > >
>> > > >
>> > > > I've already made some changes in pmu-events/* to support
>> > > > this hierarchy to see how bad the change would be.. and
>> > > > it's not that bad ;-)
>> > >
>> > > Everything has to be
On Wed, Aug 31, 2016 at 09:15:30AM -0700, Andi Kleen wrote:
> > >
> > > >
> > > > I've already made some changes in pmu-events/* to support
> > > > this hierarchy to see how bad the change would be.. and
> > > > it's not that bad ;-)
> > >
> > > Everything has to be automated, please no manual c
> >
> > >
> > > I've already made some changes in pmu-events/* to support
> > > this hierarchy to see how bad the change would be.. and
> > > it's not that bad ;-)
> >
> > Everything has to be automated, please no manual changes.
>
> sure
>
> so, if you're ok with the layout, how do you want t
On Wed, Aug 31, 2016 at 07:42:47AM -0700, Andi Kleen wrote:
> > hi,
> > I had discussion with Ingo about the state of this patchset
> > and there's one more requirement from his side - to split
> > event files into per topic files
>
> Thanks Jiri.
> >
> > I made some initial changes over latest S
> hi,
> I had discussion with Ingo about the state of this patchset
> and there's one more requirement from his side - to split
> event files into per topic files
Thanks Jiri.
>
> I made some initial changes over latest Sukadev's branch
> and came up with something like this:
Did you just split
On Mon, Jun 20, 2016 at 09:02:30PM -0700, Sukadev Bhattiprolu wrote:
> CPUs support a large number of performance monitoring events (PMU events)
> and often these events are very specific to an architecture/model of the
> CPU. To use most of these PMU events with perf, we currently have to identify
CPUs support a large number of performance monitoring events (PMU events)
and often these events are very specific to an architecture/model of the
CPU. To use most of these PMU events with perf, we currently have to identify
them by their raw codes:
perf stat -e r100f2 sleep 1
This patchs
8 matches
Mail list logo