From: Arrigo Benedetti <arrigo@vision.caltech.edu>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Disabling interrupts on a SMP system
Date: Thu, 28 Oct 2004 16:58:04 -0700 [thread overview]
Message-ID: <4181878C.20605@vision.caltech.edu> (raw)
In-Reply-To: <1099006771.29690.83.camel@gaston>
Benjamin Herrenschmidt wrote:
>On Thu, 2004-10-28 at 14:45 -0700, Arrigo Benedetti wrote:
>
>>Dear all,
>>
>>how can I (temporarily) disable all or some specific interrupts on a
>>specific CPU in an SMP system
>>from user space code? In my case this is an Apple dual G5 system.
>>
>
>You can't ... why do you want to do that ?
>
>
To achieve real-time performance in a very critical section of code.
Even after moving all the
interrupts to CPU0, there are still two interrupts running on CPU1 that
are disturbing the
execution of the time-critical code:
CPU0 CPU1
0: 45127 0 OpenPIC Level libata
25: 225 0 OpenPIC Level VIA-PMU
26: 0 0 OpenPIC Level keywest i2c
27: 0 0 OpenPIC Level ohci_hcd
28: 0 0 OpenPIC Level ohci_hcd
39: 189380 0 OpenPIC Level ide0
40: 304 0 OpenPIC Level ohci1394
41: 1288195 0 OpenPIC Level eth0
47: 0 0 OpenPIC Level GPIO1/ADB
55: 0 0 OpenPIC Edge NMI - XMON
56: 1 0 OpenPIC Edge U3->K2 Cascade
63: 15212 0 OpenPIC Level ehci_hcd, ohci_hcd,
ohci_hcd
118: 15 21134 OpenPIC Level IPI0 (call function)
119: 888 904 OpenPIC Level IPI1 (reschedule)
120: 0 0 OpenPIC Edge IPI2 (invalidate tlb)
121: 0 0 OpenPIC Edge IPI3 (xmon break)
128: 0 0 OpenPIC2 Level keywest i2c
IPI (recv/sent): 22941/22941
BAD: 1
I agree that this is not an elegant solution, but I would like to give
it a try anyway...
Thanks
-Arrigo
next prev parent reply other threads:[~2004-10-28 23:58 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 [this message]
2004-10-29 0:51 ` Benjamin Herrenschmidt
2004-10-29 10:10 ` Gabriel Paubert
2004-10-29 23:00 ` Benjamin Herrenschmidt
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=4181878C.20605@vision.caltech.edu \
--to=arrigo@vision.caltech.edu \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.