From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Livio Soares <livio@eecg.toronto.edu>
Subject: Re: [PATCH] Fix performance monitor exception in 2.6.20-series
Date: Sun, 14 Jan 2007 01:39:17 +0100 [thread overview]
Message-ID: <dd188efa1bcb288b11f0b7c601c8778a@kernel.crashing.org> (raw)
In-Reply-To: <1168734544.5011.78.camel@localhost.localdomain>
> Well, are you absolutely sure that nothing will break as a result of
> having a PMU interrupt happening right when it's not expected to ?
>
> You are basically turning the PMU interrupt into an NMI... I'm not sure
> how safe that is.
That just depends what code is run from the PMU exception.
It very much makes sense *conceptually* to have it behave
like an NMI I think -- but yeah the code run from the
exception had better behave ;-)
Segher
next prev parent reply other threads:[~2007-01-14 0:38 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 [this message]
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
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=dd188efa1bcb288b11f0b7c601c8778a@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=livio@eecg.toronto.edu \
/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).