Re: About interrupt handler

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



HI Kosta,

On Fri, Feb 24, 2012 at 1:08 PM, Dave Hylands <dhylands@xxxxxxxxx> wrote:
> Hi Kosta,
>
> On Fri, Feb 24, 2012 at 1:19 AM, Kosta Zertsekel <zertsekel@xxxxxxxxx> wrote:
>>>> I'm begin to learn the Kernel and i'm reading <<Linux kernel
>>>> development>>.It says "This is an important point, always keep in mind that
>>>> all interrupt handler has interrupted other code(possibly even another
>>>> interrupt handler on a different line)".What i am not able to understand is
>>>> how a interrupt handler be interrupted ? DID NOT it uninterrupted?
>>>
>>> It depends on the architecture and the interrupt controller being
>>> used, and the driver code itself.
>>>
>>> Normally, when an interrupt fires, that particular interrupt will be
>>> masked and your own handler won't interrupt itself, but you may very
>>> well be interrupted by other interrupts.
>>
>> Can you please point out some code for explanation?
>
> Could you be a bit more specific about what example you're looking for?

I also believe that things have changed (since I looked at this in any
detail). It seems that interrupts are now run with other interrupts
disabled.
See: http://lwn.net/Articles/364583/ and look at the IRQF_DISABLED discussion.

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


[Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Photo]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Networking]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]

Add to Google Powered by Linux