* Dedicated Interrupt handling on SMP
@ 2001-05-25 16:43 Randy
2001-05-25 20:38 ` Ingo Oeser
0 siblings, 1 reply; 2+ messages in thread
From: Randy @ 2001-05-25 16:43 UTC (permalink / raw)
To: linux-kernel
I'm trying to find the easiest way to to deidcate one CPU to responding
to a specific Interrupt request.
That CPU should only listen for that request while all other CPU should
ignore the interrupt.
Any suggestions? Do I have to muck with the IO_APIC or is there a
simpler way which I just missed?
Any help would be appreciated!
Thank you!
Randy Schumm
Please CC: answer to randys@evcom.net
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Dedicated Interrupt handling on SMP
2001-05-25 16:43 Dedicated Interrupt handling on SMP Randy
@ 2001-05-25 20:38 ` Ingo Oeser
0 siblings, 0 replies; 2+ messages in thread
From: Ingo Oeser @ 2001-05-25 20:38 UTC (permalink / raw)
To: Randy; +Cc: linux-kernel
On Fri, May 25, 2001 at 12:43:11PM -0400, Randy wrote:
> I'm trying to find the easiest way to to deidcate one CPU to responding
> to a specific Interrupt request.
> That CPU should only listen for that request while all other CPU should
> ignore the interrupt.
cat /proc/irq/*/smp_affinity
There you can select on which if the 32 CPUs Linux should handle
this IRQ.
Read Documentation/IRQ-affinity.txt for more.
Regards
Ingo Oeser
--
To the systems programmer,
users and applications serve only to provide a test load.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-05-25 20:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-05-25 16:43 Dedicated Interrupt handling on SMP Randy
2001-05-25 20:38 ` Ingo Oeser
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox