Re: [tip:perf/core] perf tools: Make Power7 events available for perf

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I wish I were as good as cursing as Linus, ccing him in case he's willing 
to donate a few choice expressions.

On Tue, 23 Jul 2013, Michael Ellerman wrote:

> On Tue, 2013-07-23 at 01:33 -0400, Vince Weaver wrote:

> > > $ size arch/powerpc/perf/power7-pmu.o
> > >    text          data     bss     dec     hex filename
> > >    3073          2720       0    5793    16a1 arch/powerpc/perf/power7-pmu.o
> > > 
> > > and after the patch is applied, it is:
> > > 
> > > $ size arch/powerpc/perf/power7-pmu.o
> > >    text          data     bss     dec     hex filename
> > >   15950         31112       0   47062    b7d6 arch/powerpc/perf/power7-pmu.o
> > 
> > 
> > so we're really going down this road?
> 
> _We_ are going down this road, at least until there is a better
> solution. You'll notice I haven't merged any events for power8.

No, you are going down this road permanently, because if you commit this, 
it becomes ABI, and we have to maintain it forever.

> x86 can do what it wants. I don't think anyone in x86 land has proposed
> putting all the events in the kernel, so you can stop worrying about
> your 300k of memory.

I thought the prime directive of perf_event was nothing in the kernel that 
wasn't generic and applied to all architectures?  Why is Power7 special?

Abusing sysfs to waste 100k of non-swappable kernel memory on every 
running Linux kernel everwhere to hold static event tables that could be a 
simple CSV file in the perf tools directory is crazy.

Especially as it's likely this becomes stable ABI, and then you'll 
promptly break it as has already happenend in the last kernel release 
with the existing in-kernel powerpc events.

> I thought it was pretty clear from the last thread that folks agreed the
> event _lists_ should be in userspace. The discovery of the PMUs should
> be done in the kernel, and that should be communicated to userspace via
> something in sys.

I agree.  So why is this patch in tip?

> What it needs now is someone with some free time to actually code it up.
> Right now that's not me.

The code exists; it's called libpfm4.  Just becase you're lazy doesn't 
mean we commit garbage code into the kenrel.

For what it's worth, as the unofficial perf_event ABI documentation 
maintainer I strongly NAK this patch.

Vince


--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Stable Commits]     [Linux Stable Kernel]     [Linux Kernel]     [Linux USB Devel]     [Linux Video &Media]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux