linux-kernel - Re: chained irq handler problems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.02.1106141202531.11814@ionos>
Date:	Tue, 14 Jun 2011 12:05:50 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Manuel Lauss <manuel.lauss@...glemail.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: chained irq handler problems

On Sun, 12 Jun 2011, Manuel Lauss wrote:
> My question is: what are the differences in interrupt handling between the
> "traditional" handler and the cascade handler case?
> I also noticed that the cascade irq (the muxer irq line to the cpu) is not
> disabled when the interrupt is serviced. Is this by design?

The normal handler, which should btw never ever be setup from an
startup callback, deals with the irq chip functions (mask, ack, eoi)
which are assigned to that irq line. The chained handler is called
directly from the low level entry code and bypasses the standard
handling mechanism. That means no chip functions are called. If your
irq chip of the primary line requires e.g. an ack, then this needs to
be done explicitely in the chained handler itself.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/