From: Martin Hicks <mort@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] turn off irqdebug by default on Altix
Date: Thu, 05 Feb 2004 18:37:28 +0000 [thread overview]
Message-ID: <20040205183728.GC19025@localhost> (raw)
In-Reply-To: <20040204152841.GB3387@localhost>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
On Wed, Feb 04, 2004 at 01:40:47PM -0600, Jack Steiner wrote:
> On Wed, Feb 04, 2004 at 02:08:05PM -0500, Martin Hicks wrote:
> >
> >
> > On Wed, Feb 04, 2004 at 11:04:43AM -0800, Chen, Kenneth W wrote:
> > > This is really confusing with two parameters that do the same thing.
> > > What will happen if someone pass noirqdebug and irqdebug at the same
> > > time?
> > >
> > > What's wrong with boot time parameter of noirqdebug?
> >
> > It just means that if you forget to pass this option then your machine
> > never boots. Well, it will boot. Eventually. Jack is a patient man,
> > and he said he never waited long enough for it to boot.
>
> Actually, I determined that a big system would never boot. Each cpu would have to
> do about 1500usec of work every 1000usec. (highly dependent on the
> system interconnect).
>
> Each clock tick, the desc->irq_count is incremented by each cpu. On a big
> system, this creates an incredibly hot cache line. On a big system, it takes
> more than a millisecond to do the update. At that point, another clock
> interrupt is already pending. Forward progress stops.
>
> Another possible approach might be to special case note_interrupt() to
> skip the update for the timer tick. (I havent actually looked at the code, but
> this should be possible).
Okay. This is certainly less messy, and is IA64 specific.
How about this patch? I just tested it on a 512p machine and it booted.
mh
--
Martin Hicks || Silicon Graphics Inc. || mort@sgi.com
[-- Attachment #2: no-timer-interrupt-in-note-interrupt.diff --]
[-- Type: text/plain, Size: 1080 bytes --]
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.1543 -> 1.1544
# arch/ia64/kernel/irq.c 1.34 -> 1.35
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 04/02/04 mort@green.i.bork.org 1.1544
# Don't debug the timer interrupt in note_interrupt(). This
# should allow forward progress on large machine with irqdebug
# enabled.
# --------------------------------------------
#
diff -Nru a/arch/ia64/kernel/irq.c b/arch/ia64/kernel/irq.c
--- a/arch/ia64/kernel/irq.c Wed Feb 4 15:43:12 2004
+++ b/arch/ia64/kernel/irq.c Wed Feb 4 15:43:12 2004
@@ -311,6 +311,10 @@
*/
static void note_interrupt(int irq, irq_desc_t *desc, irqreturn_t action_ret)
{
+ /* Don't debug the timer interrupt */
+ if (irq == IA64_TIMER_VECTOR)
+ return;
+
if (action_ret != IRQ_HANDLED) {
desc->irqs_unhandled++;
if (action_ret != IRQ_NONE)
next prev parent reply other threads:[~2004-02-05 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 15:28 [PATCH] turn off irqdebug by default on Altix Martin Hicks
2004-02-04 19:04 ` Chen, Kenneth W
2004-02-04 19:08 ` Martin Hicks
2004-02-04 19:17 ` Andrew Morton
2004-02-04 19:40 ` Jack Steiner
2004-02-04 21:32 ` Chen, Kenneth W
2004-02-05 18:37 ` Martin Hicks [this message]
2004-02-10 22:43 ` David Mosberger
2004-02-11 21:19 ` Martin Hicks
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=20040205183728.GC19025@localhost \
--to=mort@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