linux-kernel - Re: [GIT PATCH] more Driver core patches for 2.6.19

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: <20061214113311.24ba9b7f@localhost.localdomain>
Date:	Thu, 14 Dec 2006 11:33:11 +0000
From:	Alan <alan@...rguk.ukuu.org.uk>
To:	tglx@...utronix.de
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Linus Torvalds <torvalds@...l.org>, Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] more Driver core patches for 2.6.19

> > IRQ is shared with the disk driver, box dead.
> 
> Err ? 
> 
> IRQ happens
> 
> IRQ is disabled by the generic handling code
> 
> Handler is invoked and checks, whether the irq is from the device or
> not. 
>  - If not, it returns IRQ_NONE, so the next driver (e.g. disk) is
> invoked.
>  - If yes, it masks the chip on the device, which disables the chip
> interrupt line and returns IRQ_HANDLED.
> 
> In both cases the IRQ gets reenabled from the generic irq handling code
> on return, so why is the box dead ?

I wrote this before your "generic" layer was in fact explained further to
not be generic at all and involve a new driver for each device. Your
original explanation was not clear.

Alan
-
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/