From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 25 Mar 2008 19:07:00 +0100 From: Andi Kleen Subject: Re: [11/14] vcompound: Fallbacks for order 1 stack allocations on IA64 and x86 Message-ID: <20080325180700.GY2170@one.firstfloor.org> References: <20080321061703.921169367@sgi.com> <20080321061726.782068299@sgi.com> <871w63iuap.fsf@basil.nowhere.org> <20080325075106.GF2170@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org Return-Path: To: Christoph Lameter Cc: Andi Kleen , linux-mm@kvack.org, linux-kernel@vger.kernel.org, viro@ftp.linux.org.uk List-ID: On Tue, Mar 25, 2008 at 10:55:06AM -0700, Christoph Lameter wrote: > On Tue, 25 Mar 2008, Andi Kleen wrote: > > > Maybe sparse could be taught to check for this if it happens > > in a single function? (cc'ing Al who might have some thoughts > > on this). Of course if it happens spread out over multiple > > functions sparse wouldn't help neither. > > We could add debugging code to virt_to_page (or __pa) to catch these uses. Hard to test all cases. Static checking would be better. Or just not do it? I didn't think order 1 failures were that big a problem. -Andi -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org