----Original Message---- From: Peter Teoh [mailto:htmldeveloper@xxxxxxxxx] Sent: Friday, February 08, 2008 8:11 PM To: Rajat Jain Cc: kernelnewbies@xxxxxxxxxxxx; linux-newbie@xxxxxxxxxxxxxxx Subject: Re: Use of IRQF_DISABLED along with IRQF_SHARED > sorry, i am also quite confused.... > > the caller of your function handle_IRQ_event() is __do_IRQ(), which > is thus: > > if (likely(!(desc->status & IRQ_DISABLED))) { > action_ret = handle_IRQ_event(irq, > desc->action); if (!noirqdebug) > note_interrupt(irq, desc, action_ret); > } > > so what it means that only when IRQ_DISABLED is NOT SET, then > handle_IRQ_event() will be called, simulating a software-based IRQ. > > and so the above function WILL ALWAYS BE CALLED WITH IRQ_DISABLED NOT > SET (assuming there is no other caller of handle_IRQ_event()). > > errhhhh?? Am i right? Hi Peter, I think you are mistaken between IRQ_DISABLED & IRQF_DISABLED. My question was about IRQF_DISABLED. Thanks, Rajat -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
