Re: IRQ Sharing

[Remy Bohmer]

Hello Jorge,

It is not uncommon that interrupt lines are hardwired to each other on
a standard PC-board.
Therefor it is not always feasible to get rid of interrupt sharing.
Especially on-board USB adapters can easily use up to 5 interrupt
lines on a standard main-board. Also, sharing of interrupt lines (by
hardwiring them) between on-board devices and PCI slots is also common
practice.

The PCI specification explicitly states that PCI devices can share
interrupt lines, and that your drivers must be capable of handling
this.

Why is sharing a problem for you?

If you do not have special realtime requirements, it usually should be
no problem...


Remy


2007/2/6, Jorge Almeida <j-almeida@xxxxxxxxxxxxxxxxxxxx>:
> Hello to all.
>
> I'm running an application that uses several IO boards in a PCI bus.
>
> My main problem is the virtual IRQ sharing between several boards.
> I mean for example:
>         1 ethernet board IRQ = 169;
>         1 ADC card IRQ         = 169;
>
> I want to get ride of this behaviour, and changing the slot position of each
> board is not enought, to get something like (for example):
>         1 ethernet board IRQ = 169;
>         1 ADC card IRQ         = 170;
>
> Where in the kernel i can see the algorithms for the APIC system where the
> virtual IRQs are distributed? Or exist already any patch that permits to
> solve my problem?
>
> I'm using kernel 2.6.16.27, in a single machine with Intel pentium IV
> processor and chipset ICH4.
>
> Thanks for any reply.
> Greetings.
>
> --
> Jorge Almeida
> j-almeida@xxxxxxxxxxxxxxxxxxxx
> DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or without errors as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software, SA.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/