From: john stultz <johnstul@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] linux-2.5.59_lost-tick_A0
Date: 21 Jan 2003 15:48:22 -0800 [thread overview]
Message-ID: <1043192901.15683.103.camel@w-jstultz2.beaverton.ibm.com> (raw)
In-Reply-To: <3E2DD8A7.3F07C40E@digeo.com>
On Tue, 2003-01-21 at 15:32, Andrew Morton wrote:
> john stultz wrote:
> >
> > All,
> > This patch addresses the following problem: Linux cannot properly
> > handle the case where interrupts are disabled for longer then two ticks.
> >
>
> Question is: who is holding interrupts off for so long?
Unfortunately in my situation there is a card which can cause 30ms
stalls in an SMI handler. Yuck, I know. :P
> It might be better to implement a detection scheme inside
> the timer interrupt handler: if the time since last interrupt
> exceeds two ticks, whine and drop a backtrace.
>
> That backtrace will point up into the local_irq_enable() in
> the offending code, and we can go fix it?
Hmm, clever! That would be a very good check for software caused stalls.
I'll try to drop that in.
thanks for the feedback!
-john
next prev parent reply other threads:[~2003-01-21 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 22:59 john stultz
2003-01-21 23:32 ` Andrew Morton
2003-01-21 23:48 ` john stultz [this message]
2003-01-22 5:00 ` Valdis.Kletnieks
2003-01-24 23:13 ` Stephen Hemminger
2003-01-24 23:06 ` john stultz
[not found] <1043189962.15683.82.camel@w-jstultz2.beaverton.ibm.com.suse.lists.linux.kernel>
2003-01-21 23:27 ` Andi Kleen
2003-01-21 23:31 ` john stultz
2003-01-21 23:48 ` Andi Kleen
2003-01-21 23:49 ` john stultz
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=1043192901.15683.103.camel@w-jstultz2.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=akpm@digeo.com \
--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®