mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: stephane eranian <eranian@googlemail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	perfmon2-devel <perfmon2-devel@lists.sourceforge.net>
Subject: perf_events: issue with scaling information
Date: Thu, 8 Oct 2009 16:12:33 +0200	[thread overview]
Message-ID: <7c86c4470910080712v730a4c7fxbd71d97b605a1f6e@mail.gmail.com> (raw)

Hi,


With libpfm4, I have developed a set of examples which are using
perf_events to demonstrate typical counting and sampling scenarios.

In two of the sampling program, it appears time_enabled, time_running
included in the samples are incorrect.

The program notify_self.c uses IOC_REFRESH to get a notification for
each sample. The first sample comes out with time_running = time_enabled =0,
subsequent samples return non-zero information. I suspect something is
wrong initially because of IOC_REFRESH. This is using an event group.

The program task_smpl.c is sampling another process. Although the scaling
information is requested, all samples come out with time_running =
time_enabled=0.
The rest of the sample is correct, so it's not like I am not correctly
reading the
sample. The program is using an event group.

I suspect both issues may be related.

You can obtain the test programs (which are open-source!), by cloning
the GIT tree
at:
         git://perfmon2.git.sourceforge.net/gitroot/perfmon2/libpfm4


Thanks.

                 reply	other threads:[~2009-10-08 14:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7c86c4470910080712v730a4c7fxbd71d97b605a1f6e@mail.gmail.com \
    --to=eranian@googlemail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=eranian@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=perfmon2-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®