From: Ingo Molnar <mingo@elte.hu>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Papi <ptools-perfapi@cs.utk.edu>,
"David S. Miller" <davem@davemloft.net>,
Mike Galbraith <efault@gmx.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Eric Dumazet <dada1@cosmosbay.com>,
Paul Mackerras <paulus@samba.org>, Peter Anvin <hpa@zytor.com>,
"eranian@gmail.com" <eranian@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
"perfmon2-devel@lists.sourceforge.net"
<perfmon2-devel@lists.sourceforge.net>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [perfmon2] [announce] Performance Counters for Linux, v6
Date: Mon, 26 Jan 2009 23:10:38 +0100 [thread overview]
Message-ID: <20090126221038.GA7440@elte.hu> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA35F1F9374@orsmsx505.amr.corp.intel.com>
* Luck, Tony <tony.luck@intel.com> wrote:
> > - or the PMU capability is expressed as a special counter type (if it's
> > useful enough) - and then either the write() method or ioctl is extended
> > to express attributes we want to set/change while a counter is running.
>
> The product of:
> {exotic PMU modes} * {creative performance measurement ideas}
>
> will produce a large number of candidates for these special counters (at
> least on ia64 ... which has a large number of exotic PMU options).
>
> I don't think that I'm qualified to judge which of them are "useful
> enough" to warrant a special counter type.
it should certainly be done on a case by case basis. They need to be
consciously exposed not just summarily exported to user-space, because PMU
hw features have security implications so it has to be done all
explicitly.
Ingo
next prev parent reply other threads:[~2009-01-26 22:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:50 [announce] Performance Counters for Linux, v6 Ingo Molnar
2009-01-21 19:34 ` Randy Dunlap
2009-01-21 19:56 ` Ingo Molnar
2009-01-21 21:14 ` Randy Dunlap
2009-01-22 11:22 ` Karel Zak
2009-01-22 12:04 ` Karel Zak
2009-01-22 12:06 ` Ingo Molnar
2009-01-26 1:06 ` Corey Ashford
2009-01-26 9:13 ` stephane eranian
2009-01-26 15:17 ` Ingo Molnar
2009-01-26 16:55 ` stephane eranian
2009-01-26 19:13 ` Corey Ashford
2009-01-26 19:39 ` [perfmon2] " Luck, Tony
2009-01-26 22:10 ` Ingo Molnar [this message]
2009-01-26 22:15 ` Ingo Molnar
2009-01-26 23:41 ` Corey Ashford
2009-01-29 2:10 ` Corey Ashford
2009-01-29 12:32 ` stephane eranian
2009-01-29 20:01 ` Corey Ashford
2009-01-29 21:44 ` stephane eranian
2009-02-19 21:53 ` Corey Ashford
2009-02-20 8:10 ` Ingo Molnar
2009-02-20 22:38 ` Corey Ashford
2009-02-20 22:47 ` Peter Zijlstra
2009-02-20 23:04 ` Corey Ashford
2009-02-20 23:24 ` stephane eranian
2009-02-20 23:58 ` Corey Ashford
2009-02-21 0:47 ` Arnd Bergmann
2009-02-26 9:49 ` Paul Mackerras
2009-02-26 13:37 ` Arnd Bergmann
2009-03-09 1:39 ` Robert Richter
2009-03-09 23:01 ` Paul Mackerras
2009-03-10 9:44 ` Robert Richter
2009-03-10 10:29 ` Peter Zijlstra
2009-03-10 11:49 ` Paul Mackerras
2009-03-10 11:53 ` Ingo Molnar
2009-03-10 16:26 ` Robert Richter
2009-03-10 17:27 ` Ingo Molnar
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=20090126221038.GA7440@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=efault@gmx.de \
--cc=eranian@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sourceforge.net \
--cc=ptools-perfapi@cs.utk.edu \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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