linux-kernel - Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than passing to 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 for Android: free password hash cracker in your pocket

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

Message-ID: <20061002201836.GB31365@elte.hu>
Date:	Mon, 2 Oct 2006 22:18:36 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...l.org>
Cc:	David Howells <dhowells@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>, torvalds@...l.org,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	Dmitry Torokhov <dtor@...l.ru>, Greg KH <greg@...ah.com>,
	David Brownell <david-b@...bell.net>,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: [PATCH 3/3] IRQ: Maintain regs pointer globally rather than passing to IRQ handlers


* Andrew Morton <akpm@...l.org> wrote:

> I think the change is good.  But I don't want to maintain this whopper 
> out-of-tree for two months!  If we want to do this, we should just 
> smash it in and grit our teeth.  But I am a bit concerned about the 
> non-x86 architectures.  I assume they'll continue to compile-and-work?
> 
> What does Ingo think?

i agree that we should do this in one go and in Linus' tree. I suspect 
David has a script for this, so we can do it anytime for any tree, 
right?

the amount of code that truly relies on regs being present is very low. 
Mostly only sysrq type of stuff and the timer interrupt is such. Any 
arch should be able to adopt to that promptly, but i'd favor a 
switchover that works on 99% of the arches, just to have this pain over 
instantly (sans small bugs).

	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/