[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1307230129350.18266@pianoman.cluster.toy>
Date: Tue, 23 Jul 2013 01:33:04 -0400 (EDT)
From: Vince Weaver <vince@...ter.net>
To: mingo@...nel.org, hpa@...or.com, paulus@...ba.org,
linux-kernel@...r.kernel.org, acme@...hat.com,
michael@...erman.id.au, runzhen@...ux.vnet.ibm.com,
runzhew@...mson.edu, xiaoguangrong@...ux.vnet.ibm.com,
sukadev@...ux.vnet.ibm.com, tglx@...utronix.de
cc: linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf tools: Make Power7 events available for
perf
On Fri, 19 Jul 2013, tip-bot for Runzhen Wang wrote:
> perf tools: Make Power7 events available for perf
>
> This patch makes all the POWER7 events available in sysfs. So we can
> instead specify these as:
>
> $ 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?
If x86 follows this precedent we're going to end up with 300k+ of
event names in the kernel. And as a reminder, perf_event cannot
be disabled on x86, nor can it be compiled as a module. So that would
be 300k of event names in every kernel for everyone, even those not using
perf.
This belongs in userspace.
Vince
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists