-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, February 05, 2007 3:03 PM
>Nope. irq routines are a stack. if apic_in_service_vector could return
>the wrong value. ack_APIC_irq() which use the same information would
>acknowledge the wrong irq. If there was actually any danger of
>mis-computing that information I would just pass it from the interrupt
>service routine stash it in a per cpu variable and then read it out.
>But the apic already has registers doing that, so I was lazy and used
>what was available. It should be the common case that we need that
>information.
OK.
I wonder if current kernel support different cpu handle irq request for
different device at the same time.
YH
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
