Hi,
Please send me your patch and I'll look at it next week.
Thanks.
On Sat, Apr 28, 2012 at 7:39 PM, Leonardo Piga wrote:
> Hi,
>
> tr(i) is the value that I would get on the value counter for "run" if
> the counters were restarted after printing the previous sample (i-1).
>
> The same for v(i
restrictions.
-- pj
-Original Message-
From: Leonardo Piga [mailto:leonardo.p...@gmail.com]
Sent: Thursday, April 26, 2012 11:52 PM
To: perfmon2-devel@lists.sourceforge.net
Subject: [perfmon2] Multiplexing counters
Hello,
I am using libpfm 4.2 to measure about 15 performance counters on a
Hi,
tr(i) is the value that I would get on the value counter for "run" if
the counters were restarted after printing the previous sample (i-1).
The same for v(i) the value that I would get on the "raw" counter if
the counters were restarted after printing the sample(i-1).
The same applies for te
Hi,
On Sat, Apr 28, 2012 at 11:00 AM, Leonardo Piga wrote:
> I figure out the problem what the problem is.
>
> I am not sure if I can consider it a bug on the syst.c or I was just
> making wrong assumption about its output.
>
> Anyway, I wrote a document explaining the problem and possibles sol
I figure out the problem what the problem is.
I am not sure if I can consider it a bug on the syst.c or I was just
making wrong assumption about its output.
Anyway, I wrote a document explaining the problem and possibles solutions.
If it is actually a bug I can send my patch that samples the act
Hello,
I am using libpfm 4.2 to measure about 15 performance counters on a
AMD Barcelona CPU. I am able to collect 5 performance counter without
multiplexing.
However, when multiplexing I am getting "negative" delta values using
the syst from perf_examples.
Here is an example:
Sample n
"core" :
