From: David Woodhouse <dwmw2@infradead.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Livio Soares <livio@eecg.toronto.edu>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Fix performance monitor exception in 2.6.20-series
Date: Mon, 15 Jan 2007 11:14:20 +0800 [thread overview]
Message-ID: <1168830860.9415.284.camel@shinybook.infradead.org> (raw)
In-Reply-To: <17834.60612.793025.590958@cargo.ozlabs.ibm.com>
On Mon, 2007-01-15 at 13:53 +1100, Paul Mackerras wrote:
> Different PMU, I think; they are talking about the Performance Monitor
> Unit in POWERx cpus.
Ah, OK. That makes the "doesn't do anything you can't do in an NMI"
assessment make a little more sense to me.
Still, might be worth thinking about whether we can make the Apple PMU
into an NMI to help prevent the error case I mentioned.
--
dwmw2
prev parent reply other threads:[~2007-01-15 3:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 15:40 [PATCH] Fix performance monitor exception in 2.6.20-series Livio Soares
2007-01-14 0:29 ` Benjamin Herrenschmidt
2007-01-14 0:39 ` Segher Boessenkool
2007-01-14 17:56 ` Livio Soares
2007-01-15 2:40 ` David Woodhouse
2007-01-15 2:53 ` Paul Mackerras
2007-01-15 3:14 ` David Woodhouse [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=1168830860.9415.284.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=livio@eecg.toronto.edu \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).