Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755260AbYCXTz1 (ORCPT ); Mon, 24 Mar 2008 15:55:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751952AbYCXTzH (ORCPT ); Mon, 24 Mar 2008 15:55:07 -0400 Received: from relay1.sgi.com ([192.48.171.29]:53370 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753720AbYCXTzG (ORCPT ); Mon, 24 Mar 2008 15:55:06 -0400 Date: Mon, 24 Mar 2008 12:53:19 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Andi Kleen cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [11/14] vcompound: Fallbacks for order 1 stack allocations on IA64 and x86 In-Reply-To: <871w63iuap.fsf@basil.nowhere.org> Message-ID: References: <20080321061703.921169367@sgi.com> <20080321061726.782068299@sgi.com> <871w63iuap.fsf@basil.nowhere.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 874 Lines: 21 On Fri, 21 Mar 2008, Andi Kleen wrote: > The traditional reason this was discouraged (people seem to reinvent > variants of this patch all the time) was that there used > to be drivers that did __pa() (or equivalent) on stack addresses > and that doesn't work with vmalloc pages. > > I don't know if such drivers still exist, but such a change > is certainly not a no-brainer I thought that had been cleaned up because some arches already have virtually mapped stacks? This could be debugged by testing with CONFIG_VFALLBACK_ALWAYS set. Which results in a stack that is always vmalloc'ed and thus the driver should fail. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/