linux-kernel - Re: [PATCH/RFC] perfcounters: record time running and time enabled for each counter

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:	Sat, 21 Mar 2009 09:30:40 +1100
From:	Paul Mackerras <paulus@...ba.org>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH/RFC] perfcounters: record time running and time enabled
 for each counter

Peter Zijlstra writes:

> On Fri, 2009-03-20 at 23:07 +1100, Paul Mackerras wrote:
> > Impact: new functionality
> > 
> > Currently, if there are more counters enabled than can fit on the CPU,
> > the kernel will multiplex the counters on to the hardware using
> > round-robin scheduling.  That isn't too bad for sampling counters, but
> > for counting counters it means that the value read from a counter
> > represents some unknown fraction of the true count of events that
> > occurred while the counter was enabled.
> > 
> > This remedies the situation by keeping track of how long each counter
> > is enabled for, and how long it is actually on the cpu and counting
> > events.  These times are recorded in nanoseconds using the task clock
> > for per-task counters and the cpu clock for per-cpu counters.
> 
> Can't we do this by simply adding some software counters? A task local
> to each group and a task local on its own.
> 
> Since the solo task local will always be scheduled, you can get the
> sampling fraction by comparing the group task local one to the solo one.

You can get time_running that way but you can't really get
time_enabled accurately in general, since there's no way to enable or
disable two groups simultaneously.  (Yes, in the special case where
you are doing self-monitoring and you have no other counters, you can
use prctl(PR_TASK_PERF_COUNTERS_{EN,DIS}ABLE), but that's not a
general solution.)

The other thing is that the two extra software counters will add
overhead, whereas my patch will add negligible overhead - just some
integer arithmetic and accesses to cache lines which will already be
in exclusive state due to the stores we're already doing to things
such as counter->state.

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