From: Vince Weaver <vince@deater.net>
To: mingo@kernel.org, hpa@zytor.com, paulus@samba.org,
linux-kernel@vger.kernel.org, acme@redhat.com,
michael@ellerman.id.au, runzhen@linux.vnet.ibm.com,
runzhew@clemson.edu, xiaoguangrong@linux.vnet.ibm.com,
sukadev@linux.vnet.ibm.com, tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf tools: Make Power7 events available for perf
Date: Tue, 23 Jul 2013 01:33:04 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1307230129350.18266@pianoman.cluster.toy> (raw)
In-Reply-To: <tip-cfe0d8ba14a1d98245b371e486c68f37eba1ca52@git.kernel.org>
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
next prev parent reply other threads:[~2013-07-23 5:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 8:14 [PATCH v3 0/2] perf tools: Power7 events name available for perf Runzhen Wang
2013-06-28 8:14 ` Runzhen Wang
2013-06-28 8:14 ` [PATCH v3 1/2] perf tools: fix a typo of a Power7 event name Runzhen Wang
2013-06-28 8:14 ` Runzhen Wang
2013-07-12 8:51 ` [tip:perf/urgent] " tip-bot for Runzhen Wang
2013-06-28 8:14 ` [PATCH v3 2/2] perf tools: Make Power7 events available for perf Runzhen Wang
2013-06-28 8:14 ` Runzhen Wang
2013-07-19 7:44 ` [tip:perf/core] " tip-bot for Runzhen Wang
2013-07-23 5:33 ` Vince Weaver [this message]
2013-07-23 5:56 ` Michael Ellerman
2013-07-23 21:38 ` Vince Weaver
2013-07-25 13:41 ` Michael Ellerman
2013-07-26 4:25 ` Vince Weaver
2013-07-01 1:53 ` [PATCH v3 0/2] perf tools: Power7 events name " Michael Ellerman
2013-07-01 1:53 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1307230129350.18266@pianoman.cluster.toy \
--to=vince@deater.net \
--cc=acme@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=runzhen@linux.vnet.ibm.com \
--cc=runzhew@clemson.edu \
--cc=sukadev@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=xiaoguangrong@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.