mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@serpentine.com>
To: eranian@hpl.hp.com
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] 2.6.16-rc1 perfmon2 patch for review
Date: Thu, 26 Jan 2006 10:23:13 -0800	[thread overview]
Message-ID: <1138299793.12632.46.camel@serpentine.pathscale.com> (raw)
In-Reply-To: <20060126054345.GC10962@frankl.hpl.hp.com>

On Wed, 2006-01-25 at 21:43 -0800, Stephane Eranian wrote:

> This one contains statistics about perfmon such as PMU model, number of active
> sessions, and also a bunch of per-cpu statistics (see attached file).
> 
> $ cat /proc/perfmon
> perfmon version            : 2.2
> PMU model                  : Intel Pentium M
> PMU description version    : 1.0
> counter width              : 31
> loaded per-thread sessions : 0
> loaded sys-wide   sessions : 0
> current smpl buffer memory : 0
> format                     : d1-39-b2-9e-62-e8-40-e4-b4-02-73-07-87-92-e9-37 default_format2
> CPU0   total ovfl intrs    : 0
> CPU0     spurious intrs    : 0
> CPU0     replay   intrs    : 0
> CPU0     regular  intrs    : 0
> CPU0   overflow cycles     : 0
> CPU0   overflow phase1     : 0
> CPU0   overflow phase2     : 0
> CPU0   overflow phase3     : 0
> CPU0   smpl handler calls  : 0
> CPU0   smpl handler cycles : 0
> CPU0   set switch count    : 0
> CPU0   set switch cycles   : 0
> CPU0   handle timeout      : 0
> CPU0   owner task          : -1
> CPU0   owner context       : 00000000
> CPU0   activations         : 0

Is there any reason you might need those per-CPU statistics in an atomic
snapshot form?  That seems unlikely, off the top of my head.  You could
either have a per-CPU directory with a file for each counter, which
seems cleanest, or a per-CPU file with all counters and the name of
each, although the format wants cleaning compared to what you have now.

	<b


  reply	other threads:[~2006-01-26 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 15:20 Stephane Eranian
2006-01-20 16:47 ` Bryan O'Sullivan
2006-01-24 15:09   ` Stephane Eranian
2006-01-25 20:08     ` Bryan O'Sullivan
2006-01-25 23:52       ` Greg KH
2006-01-26  4:55         ` Stephane Eranian
2006-01-26  5:24           ` Greg KH
2006-01-26  5:43             ` Stephane Eranian
2006-01-26 18:23               ` Bryan O'Sullivan [this message]
2006-01-27  0:14               ` Greg KH

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=1138299793.12632.46.camel@serpentine.pathscale.com \
    --to=bos@serpentine.com \
    --cc=eranian@hpl.hp.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome