linux-kernel - Re: [PATCH 0/9] Remove 'irq' argument from all irq handlers

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]

Date:	Fri, 19 Oct 2007 21:07:22 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Jeff Garzik <jeff@...zik.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/9] Remove 'irq' argument from all irq handlers


* Eric W. Biederman <ebiederm@...ssion.com> wrote:

> > thanks for doing this.
> 
> Yes.  keeping this alive is good.
> 
> The practical question is how do we make this change without breaking 
> the drivers that use their irq argument.

the get_irq_regs() approach worked out really well. We should do a 
get_irq_nr() and be done with it?

(Then once the mechanic conversion has been done we could eliminate all 
uses of get_irq_nr() and remove the small overhead it takes to maintain 
this per-cpu value in the irq entry layer.)

full ACK on the concept from me too. Please go ahead! :)

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