> If you don't care about sampling and only care about totals, then you
> can just open the events concurrently *without* grouping them, as I
> stated previously.
perf record doesn't really support that. We need some group reader
that runs regularly. The best choice for the leader is a CPU sample
On Sat, Apr 18, 2015 at 01:47:06AM +0100, Andi Kleen wrote:
> > ... which would give you arbitrary skew, because one counter is
> > free-running and the other is not (when scheduling a context in or out we
> > stop
> > the PMU)
>
> Everyone just reads the counter and subtracts it from
> the last
> ... which would give you arbitrary skew, because one counter is
> free-running and the other is not (when scheduling a context in or out we stop
> the PMU)
Everyone just reads the counter and subtracts it from
the last value they've seen.
That's the same how any other shared free running counte
On Thu, Apr 16, 2015 at 10:23:42PM +0100, Andi Kleen wrote:
> > From my PoV that makes sense. One is CPU-affine, the other is not, and
> > the two cannot be scheduled in the same PMU transaction by the nature of
> > the hardware. Fundamentally, you cannot provide group semantics due to
> > this.
>
> From my PoV that makes sense. One is CPU-affine, the other is not, and
> the two cannot be scheduled in the same PMU transaction by the nature of
> the hardware. Fundamentally, you cannot provide group semantics due to
> this.
Actually you can. Just use it like a free running counter, and the
di
On Thu, Apr 16, 2015 at 05:31:40PM +0100, Mark Rutland wrote:
> Hi,
>
> If you're going to fundamentally change the behaviour of
> perf_invalid_context, please Cc authors of other system PMU drivers.
> Intel aren't the only ones with such PMUs.
>
> For instance, this affects the ARM CCI and CCN P
> Even if you ignore the fundamental semantics of groups, there are other
> problems with allowing shared contexts:
>
> * The *_txn functions only get called on the group leader's PMU. If your
> system PMU has these functions, they are not called.
>
> * Event rotation is per ctx, but now you co
Hi,
If you're going to fundamentally change the behaviour of
perf_invalid_context, please Cc authors of other system PMU drivers.
Intel aren't the only ones with such PMUs.
For instance, this affects the ARM CCI and CCN PMU drivers.
On Wed, Apr 15, 2015 at 08:56:11AM +0100, Kan Liang wrote:
> Fr
>
> On Wed, Apr 15, 2015 at 03:56:11AM -0400, Kan Liang wrote:
> > The event count only be read when the event is already sched_in.
>
> Yeah, so no. This breaks what groups are. Group events _must_ be co-
> scheduled. You cannot guarantee you can schedule events from another
> PMU.
Why? I thin
On Wed, Apr 15, 2015 at 03:56:11AM -0400, Kan Liang wrote:
> The event count only be read when the event is already
> sched_in.
Yeah, so no. This breaks what groups are. Group events _must_ be
co-scheduled. You cannot guarantee you can schedule events from another
PMU.
Also, I cannot see how this
On Wed, Apr 15, 2015 at 06:21:11PM +0200, Andi Kleen wrote:
> On Wed, Apr 15, 2015 at 06:15:28PM +0200, Peter Zijlstra wrote:
> > On Wed, Apr 15, 2015 at 03:56:11AM -0400, Kan Liang wrote:
> > > From: Kan Liang
> > >
> > > The pmu marked as perf_invalid_context don't have any state to switch on
>
On Wed, Apr 15, 2015 at 06:15:28PM +0200, Peter Zijlstra wrote:
> On Wed, Apr 15, 2015 at 03:56:11AM -0400, Kan Liang wrote:
> > From: Kan Liang
> >
> > The pmu marked as perf_invalid_context don't have any state to switch on
> > context switch. Everything is global. So it is OK to be part of sw/
On Wed, Apr 15, 2015 at 03:56:11AM -0400, Kan Liang wrote:
> From: Kan Liang
>
> The pmu marked as perf_invalid_context don't have any state to switch on
> context switch. Everything is global. So it is OK to be part of sw/hw
> groups.
> In sched_out/sched_in, del/add must be called, so the
> per
From: Kan Liang
The pmu marked as perf_invalid_context don't have any state to switch on
context switch. Everything is global. So it is OK to be part of sw/hw
groups.
In sched_out/sched_in, del/add must be called, so the
perf_invalid_context event can be disabled/enabled accordingly during
contex
14 matches
Mail list logo