public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@frankl.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Spurious PMU Interrupt
Date: Wed, 18 Dec 2002 01:01:36 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805608@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805607@msgid-missing>

Ray,

On Tue, Dec 17, 2002 at 06:53:31PM -0600, Ray Bryant wrote:
> Stephane,
> 
> I am getting one log message of the following type per CPU every time I
> run a system-wide sampling session:
> 
> kernel: perfmon: Spurious PMU overflow interrupt on CPUxx: pmc0=0x1
> owner\000000000000000 
> 

This happens on McKinley only, this is not an error and can be ignored.
In fact in the latest version of the kernel (2.4.20), I removed the printk() 
to avoid confusion. This is due do an erratum in the McKinley PMU. The problem
is in fact a desired feature which got cast as an error due to a bug in  
the Itanium PMU. Basically, if you set the freeze bit when it is not set
you'll get a PMU interrupt. This is what happens at the end of a monitoring
session in the current perfmon codebase for both 2.4 and 2.5. I think
you can see how this "bug" is in fact a feature which could be use during
the context switch, for instance.

So you can ignore the problem. The new perfmon codebase that I am working
on will never set the freeze bit explicitely anymore, so the "problem" will
go away.

-- 
-Stephane


      reply	other threads:[~2002-12-18  1:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-18  0:53 [Linux-ia64] Spurious PMU Interrupt Ray Bryant
2002-12-18  1:01 ` Stephane Eranian [this message]

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=marc-linux-ia64-105590709805608@msgid-missing \
    --to=eranian@frankl.hpl.hp.com \
    --cc=linux-ia64@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