Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753709AbZFFA5I (ORCPT ); Fri, 5 Jun 2009 20:57:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752399AbZFFA4z (ORCPT ); Fri, 5 Jun 2009 20:56:55 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:54420 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752001AbZFFA4y (ORCPT ); Fri, 5 Jun 2009 20:56:54 -0400 Date: Fri, 05 Jun 2009 17:56:56 -0700 (PDT) Message-Id: <20090605.175656.95336229.davem@davemloft.net> To: benh@kernel.crashing.org Cc: subrata@linux.vnet.ibm.com, sachinp@linux.vnet.ibm.com, sfr@canb.auug.org.au, greg@kroah.com, linux-kernel@vger.kernel.org, Linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org, paulus@samba.org, Geert.Uytterhoeven@sonycom.com, geert@linux-m68k.org Subject: Re: [BUILD FAILURE 01/04] Next June 04:PPC64 randconfig [drivers/staging/comedi/drivers.o] From: David Miller In-Reply-To: <1244244749.31984.16.camel@pasglop> References: <20090605182625.24093.7808.sendpatchset@elm3a191.beaverton.ibm.com> <1244244749.31984.16.camel@pasglop> X-Mailer: Mew version 6.2.51 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=utf-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by alpha.home.local id n560vh54007746 Content-Length: 861 Lines: 20 From: Benjamin Herrenschmidt Date: Sat, 06 Jun 2009 09:32:29 +1000 > >> I tried this. But, with some catch. ‘PAGE_KERNEL_NOCACHE’ seems to be the >> choice for majority of architectures like frv, m32r, sh, x86, etc, as Geert >> mentions below. However, i believe POWERPC defines it as ‘PAGE_KERNEL_NC‘ >> found at arch/powerpc/include/asm/pte-common.h. >> >> Paul/Banjamin, >> Can you please confirm this ? > > Read my reply to Greg. Why the heck are you trying to map memory > non-cacheable in the first place ? I agree, this is extremely fishy. I guess the issue is that the driver wants consistent DMA memory but wants to allocate a huge area vmap() style. ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?