From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: Arrigo Benedetti <arrigo@bologna.vision.caltech.edu>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Disabling interrupts on a SMP system
Date: Sat, 30 Oct 2004 09:00:06 +1000 [thread overview]
Message-ID: <1099090806.29689.140.camel@gaston> (raw)
In-Reply-To: <20041029101017.GA28149@iram.es>
> I alway wondered why the decrementer interrupts are not listed,
> actually. Perhaps even with a count of the decrementer interrupts
> which result in multiple updates of jiffies, because they indicate
> that something has avery high latency.
>
> BTW, on my Pismo, the number of bad interrupts is amazing:
>
> .../...
>
> BAD: 21458276
>
> in about one week uptime, but over half the time sleeping.
>
> I have a fix for that, but it's not yet ready for submission.
> I might find time over the week-end.
Ah ok, what is it ? Those seem to be "short" interrupts, they don't
happen on my tipb but they do happen on paul's older one (same mobo as
Pismo).
Looks like between clearing the irq source and exiting the handler, the
IRQ line stays asserted a bit longer or so ...
BTW, We should remove the cruft of early/late eoi too while we are at
it. A single "late" EOI is all we need. The MPIC will latch an edge irq
coming in between the ACK and the EOI and we don't want the CPU priority
to drop too early.
Ben.
next prev parent reply other threads:[~2004-10-29 23:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 21:45 Disabling interrupts on a SMP system Arrigo Benedetti
2004-10-28 23:39 ` Benjamin Herrenschmidt
2004-10-28 23:58 ` Arrigo Benedetti
2004-10-29 0:51 ` Benjamin Herrenschmidt
2004-10-29 10:10 ` Gabriel Paubert
2004-10-29 23:00 ` Benjamin Herrenschmidt [this message]
2004-11-03 12:30 ` Gabriel Paubert
2004-11-03 22:11 ` Benjamin Herrenschmidt
2004-11-04 12:57 ` Gabriel Paubert
2004-11-15 11:55 ` Gabriel Paubert
2004-10-29 17:32 ` Arrigo Benedetti
2004-10-29 23:11 ` Benjamin Herrenschmidt
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=1099090806.29689.140.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=arrigo@bologna.vision.caltech.edu \
--cc=linuxppc-dev@ozlabs.org \
--cc=paubert@iram.es \
/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;
as well as URLs for NNTP newsgroup(s).