linux-kernel - Re: [patch] x86 supports NO

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: <200806232339.25926.david-b@pacbell.net>
Date:	Mon, 23 Jun 2008 23:39:25 -0700
From:	David Brownell <david-b@...bell.net>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	benh@...nel.crashing.org, lkml <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, hpa@...or.com
Subject: Re: [patch] x86 supports NO_IRQ convention

On Monday 23 June 2008, Robert Hancock wrote:
> IRQ 0 is only used by 
> architecture-specific code and is not sharable,

That seems to be the consensus, and it does reflect
how it's used on all architectures I happen to have
seen it in use.

Leaving the question then of what should happen to
the existing NO_IRQ code ... none of the declarations
seems to have a comment "deprecated, don't use this"
and most of the defined values are nonzero.

Some docs appear to be missing.
--
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/