From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: PMU and timer interrupts
Date: Mon, 13 Feb 2006 20:13:06 +0000 [thread overview]
Message-ID: <200602132013.k1DKD6g13617@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060209171648.GA26865@frankl.hpl.hp.com>
Stephane Eranian wrote on Monday, February 13, 2006 12:02 PM
> On Fri, Feb 10, 2006 at 03:04:57PM -0800, Chen, Kenneth W wrote:
> > In fact, most of the interrupts having SA_INTERRUPT flag set. So the
> > blind spots you worried about for PMU is a lot wider. For example, on
> > my system, serial, e1000, mpt fusion, qla2300 interrupts all have that
> > flag set. Looks like kernel executes these handlers with irq disabled
> > all the way through.
> >
> Looking at my 2.6.16-rc1, it appears that neither e1000 nor mpt fusion
> are using SA_INTERRUPT anymore. The qla2xxx still does, though.
Yeah, I think you are correct.
- Ken
next prev parent reply other threads:[~2006-02-13 20:13 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 [this message]
2006-02-13 20:32 ` Chen, Kenneth W
2006-02-13 21:26 ` Keith Owens
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=200602132013.k1DKD6g13617@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.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