linux-kernel - Re: Performance counter API review was [patch] Performance Counters for Linux, v3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 3 Feb 2009 10:53:02 -0600
From:	Maynard Johnson <mpjohn@...ibm.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <andi@...stfloor.org>,
	Arjan van de Veen <arjan@...radead.org>,
	Carl Love <carll@...ibm.com>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Eric Dumazet <dada1@...mosbay.com>,
	"David S. Miller" <davem@...emloft.net>,
	Stephane Eranian <eranian@...glemail.com>,
	Peter Anvin <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>, Paul Mackerras <paulus@...ba.org>,
	Robert Richter <robert.richter@....com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Performance counter API review was [patch] Performance Counters for
 Linux, v3

Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote on 02/02/2009 02:33:01 PM:

> On Mon, 2009-02-02 at 12:03 -0800, Corey Ashford wrote:
> > Andi Kleen wrote:
> > [snip]
> > > - Global tracing. Right now there seem to be two modi: per task and
> > > per CPU. But a common variant is global tracing of all CPUs. While
this
> > > could be in theory done right now by attaching to each CPU
> > > this has the problem that it doesn't interact very well with CPU
> > > hot plug. The application would need to poll for additional/lost
> > > CPUs somehow and then re-attach to them (or detach). This would
> > > likely be quite clumsy and slow. It would be better if the
> kernel supported
> > > that better.
> > >
> > > Or alternative here is to do nothing and keep oprofile for that job
> > > (which it doesn't do that badly)
> > >
> >
> > This issue is of particular interest to us, from the IBM Power
toolchain
> > perspective.
> >
> > Ingo, do you think it would be feasible to add an ability to open a
> > single file descriptor that could give global counting (and sampling)
on
> > all CPU's?  I realize this would entail creating a context per cpu in
> > the kernel.
> >
> > How to present the count data back to user space is another issue.  For

> > example, do you sum the counts of a particular event type across all
> > CPUs or do you keep them separate, and have the user space app read
them
> > up per-cpu  (perhaps not knowing exactly which cpu they come from)?
> >
> > I realize that perfmon doesn't have this ability either, it's currently

> > per-cpu as well for global counting.
> >
> > But it seems as long as you are going so far as providing a thread
> > inheritance feature (which I assume uses a summing approach for
> > providing counts back to user space), that this "pan-cpu" counting
> > feature might not be too difficult to implement.  It sure would
simplify
> > the life of user space apps, as Andi said.
>
> Doing a single fd for all cpus is going to suck chunks because its going
> to be a global serialization point.
Right, a single fd is probably not the way to go, since some users are
going to want to see per-cpu counts.  The user tool can do the accumulation
for global counts.  However, expecting the user tool to manage the opening
of per-cpu fds is less than ideal for several reasons, as has already been
stated by others.

I suggest allowing cpu=-1 and pid=-1 to be passed on the perf_counter_open
call (which should require root authority for security reasons -- as does
cpu=<cpu#> and pid=-1).  With such a capability, the OProfile kernel driver
code could be re-written on top of PCL instead of continuing to maintain so
much processor-specific code (which no doubt would duplicate a lot of
processor-specific PCL code).  And, of course, this capability could be
used by other performance tools, as well.
>
> Also, why would you be profiling while doing a hotplug? Both cpu
> profiling, and hotplug, are administrator operations, just don't do
> that.
Surely you jest.  Profiling, an administrator operation?  Maybe on your
laptop.

-Maynard
>
> The inheritance thing will also suffer this issue, if you're going to do
> reads of your fds at any other point than at the end -- it will have to
> walk the whole inheritance tree and sum all the values (or propagate
> interrupts up the tree). Which sounds rather expensive.
>
>
>

--
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/