From: Michael Ellerman <michael@ellerman.id.au>
To: Vince Weaver <vince@deater.net>
Cc: mingo@kernel.org, hpa@zytor.com, paulus@samba.org,
linux-kernel@vger.kernel.org, acme@redhat.com,
runzhen@linux.vnet.ibm.com, runzhew@clemson.edu,
xiaoguangrong@linux.vnet.ibm.com, sukadev@linux.vnet.ibm.com,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf tools: Make Power7 events available for perf
Date: Tue, 23 Jul 2013 15:56:09 +1000 [thread overview]
Message-ID: <1374558969.5545.30.camel@concordia> (raw)
In-Reply-To: <alpine.DEB.2.02.1307230129350.18266@pianoman.cluster.toy>
On Tue, 2013-07-23 at 01:33 -0400, Vince Weaver wrote:
> 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?
_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.
> 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.
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 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.
What it needs now is someone with some free time to actually code it up.
Right now that's not me.
cheers
next prev parent reply other threads:[~2013-07-23 5:56 UTC|newest]
Thread overview: 11+ 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 ` [PATCH v3 1/2] perf tools: fix a typo of a Power7 event name 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-07-19 7:44 ` [tip:perf/core] " tip-bot for Runzhen Wang
2013-07-23 5:33 ` Vince Weaver
2013-07-23 5:56 ` Michael Ellerman [this message]
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
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=1374558969.5545.30.camel@concordia \
--to=michael@ellerman.id.au \
--cc=acme@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--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=vince@deater.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox