From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: PMU and timer interrupts
Date: Mon, 13 Feb 2006 21:26:47 +0000 [thread overview]
Message-ID: <21300.1139866007@ocs3> (raw)
In-Reply-To: <20060209171648.GA26865@frankl.hpl.hp.com>
Stephane Eranian (on Mon, 13 Feb 2006 12:12:39 -0800) wrote:
>Jes seems to believe than this is more historical than anything for qla2xxx.
>Now what about the timer interrupt, why does it really need SA_INTERRUPT especially
>given that it is so high priority and with the TPR mechanism. IT seems to be
>a protection against MCA, IPI, IPI_RESCHEDULE based on the current layout.
Nit pick, the time interrupt will hold off any MCA slave rendezvous,
but not the MCA monarch event. The latter is not masked by the kernel,
except where it is already processing an MCA monarch or INIT
monarch/slave event.
next prev parent reply other threads:[~2006-02-13 21:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 17:16 PMU and timer interrupts Stephane Eranian
2006-02-09 18:16 ` Jack Steiner
2006-02-09 18:20 ` Luck, Tony
2006-02-09 18:39 ` Stephane Eranian
2006-02-09 19:10 ` Jack Steiner
2006-02-09 19:11 ` Stephane Eranian
2006-02-10 13:35 ` Stephane Eranian
2006-02-10 13:54 ` Jes Sorensen
2006-02-10 20:33 ` Chen, Kenneth W
2006-02-10 21:22 ` Stephane Eranian
2006-02-10 23:04 ` Chen, Kenneth W
2006-02-10 23:21 ` Stephane Eranian
2006-02-10 23:26 ` Jes Sorensen
2006-02-13 10:38 ` Stephane Eranian
2006-02-13 10:53 ` Jes Sorensen
2006-02-13 20:01 ` Stephane Eranian
2006-02-13 20:12 ` Stephane Eranian
2006-02-13 20:13 ` Chen, Kenneth W
2006-02-13 20:32 ` Chen, Kenneth W
2006-02-13 21:26 ` Keith Owens [this message]
2006-02-13 22:49 ` Chen, Kenneth W
2006-02-13 23:46 ` Stephane Eranian
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=21300.1139866007@ocs3 \
--to=kaos@sgi.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