public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vince@deater.net>
Cc: Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] perf_counter: Add p6 PMU
Date: Thu, 09 Jul 2009 00:14:24 +0200	[thread overview]
Message-ID: <1247091264.9777.311.camel@twins> (raw)
In-Reply-To: <1247089529.16156.27.camel@laptop>

On Wed, 2009-07-08 at 23:45 +0200, Peter Zijlstra wrote:
> On Wed, 2009-07-08 at 17:46 -0400, Vince Weaver wrote:
> > On Wed, 8 Jul 2009, Peter Zijlstra wrote:
> > 
> > >   doesn't sound like the right kind of event.. but then, it doesn't
> > >   have anything better either.
> > 
> > Is there a way to specify "invalid event"?  Just setting it to 0 doesn't 
> > work, on the Pentium Pro event 0 returns what looks like essentially
> > random numbers.
> 
> Hmm, bugger. I was assuming writing 0 to the evensel would disable the
> counter. Apparently that only works for eventsel1, which would mean we
> cannot run counter1 without counter0. That means we'd need to do a
> counter swap at times... :/

Ooh, we can instead use a counter that's specified to not count anything
for 'disabling' the counter, like event 0x2E with unit mask 0.



  reply	other threads:[~2009-07-08 22:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 20:06 [patch] perf_counter: Add p6 PMU Vince Weaver
2009-07-07 20:34 ` Peter Zijlstra
2009-07-07 23:24 ` Ingo Molnar
2009-07-08 11:15 ` Peter Zijlstra
2009-07-08 21:46   ` Vince Weaver
2009-07-08 21:45     ` Peter Zijlstra
2009-07-08 22:14       ` Peter Zijlstra [this message]
2009-07-09 13:24         ` Peter Zijlstra
2009-07-10 10:40     ` [tip:perfcounters/core] perf_counter: Add P6 PMU support tip-bot for Vince Weaver

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=1247091264.9777.311.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=vince@deater.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