8 Aug
2004
8 Aug
'04
1:41 a.m.
Lee Revell wrote:
On Sun, 2004-08-08 at 00:30, Luke Yelavich wrote:
Is there any way to do this on a 2.4 kernel? Like say,
2.4.26-ll.rhfc1.ccrma, or is this already covered with how Fernando
configures the kernel?
Rick B
On Sun, Aug 08, 2004 at 02:27:02PM EST, Lee Revell
wrote:
Just echo 0 > /proc/irq/foo/bar/threaded.
root@mindpipe:/home/rlrevell/testresults# find /proc/irq -name threaded -print -a -exec
cat {} \;
/proc/irq/15/ide1/threaded
1
/proc/irq/14/ide0/threaded
1
/proc/irq/12/uhci_hcd/threaded
1
/proc/irq/11/eth0/threaded
1
/proc/irq/11/uhci_hcd/threaded
1
/proc/irq/10/EMU10K1/threaded
0
/proc/irq/10/uhci_hcd/threaded
1
/proc/irq/8/rtc/threaded
0
/proc/irq/1/i8042/threaded
1
Lee
This ensures that those interrupts have the
highest priority of anything
on the system. The soundcard is important for obvious reasons, and the
RTC is used for midi timing. These are also the only two devices on the
system (other than the timer irq 0 which cannot be made threaded) whose
nature imposes an inherehent real time constraint on the system. For
any other device that can raise an interrupt, we can process it at our
leisure, but if we don't handle the sound card interrupt within the
period time we are hosed.
Sorry, I haven't really been following the thread, but how do you set
interrupts
to be non-threaded?