From: Chuck Ebbert <76306.1226@compuserve.com>
To: Bjorn Steinbrink <B.Steinbrink@gmx.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i386: Fix softirq accounting with 4K stacks
Date: Mon, 26 Jun 2006 18:54:00 -0400 [thread overview]
Message-ID: <200606261856_MC3-1-C384-91D6@compuserve.com> (raw)
In-Reply-To: <20060625184244.GA11921@atjola.homenet>
On Sun, 25 Jun 2006 20:42:44 +0200, Bjorn Steinbrink wrote:
> Btw, which path do apic irqs go? I stumbled across the nmi stuff, but
> didn't see anything special for the apic irqs.
arch/i386/kernel/entry.S has the macro BUILD_INTERRUPT(name, nr).
The code that uses this macro is in arch/i386/mach-*/entry_arch.h.
The macro prepends "smp_" to the name passed to the macro and the
generated asm code calls that function after saving registers, etc.
arch/i386/kernel/apic.c::apic_intr_init() calls set_intr_gate() to
point some of the interrupt gates at the correct functions.
--
Chuck
"You can't read a newspaper if you can't read." --George W. Bush
next reply other threads:[~2006-06-26 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 22:54 Chuck Ebbert [this message]
2006-06-27 0:57 ` Björn Steinbrink
-- strict thread matches above, loose matches on Subject: below --
2006-06-24 5:59 Measuring tools - top and interrupts Mike Galbraith
2006-06-24 6:26 ` Mike Galbraith
2006-06-24 9:21 ` Björn Steinbrink
2006-06-24 9:51 ` Mike Galbraith
2006-06-24 11:41 ` Mike Galbraith
2006-06-24 15:40 ` Björn Steinbrink
2006-06-24 16:23 ` Mike Galbraith
2006-06-24 19:25 ` Björn Steinbrink
2006-06-25 5:06 ` Mike Galbraith
2006-06-25 11:12 ` Björn Steinbrink
2006-06-25 14:24 ` [PATCH] i386: Fix softirq accounting with 4K stacks Björn Steinbrink
2006-06-25 15:15 ` Arjan van de Ven
2006-06-25 17:44 ` Mike Galbraith
2006-06-25 17:43 ` Arjan van de Ven
2006-06-25 18:42 ` Björn Steinbrink
2006-06-26 2:23 ` Mike Galbraith
2006-06-26 3:05 ` Mike Galbraith
2006-06-26 17:58 ` Björn Steinbrink
2006-06-27 10:09 ` Mike Galbraith
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=200606261856_MC3-1-C384-91D6@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=B.Steinbrink@gmx.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®