From: David Miller <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]
Date: Fri, 05 Jun 2009 17:56:56 -0700 (PDT) [thread overview]
Message-ID: <20090605.175656.95336229.davem@davemloft.net> (raw)
In-Reply-To: <1244244749.31984.16.camel@pasglop>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: Text/Plain; charset=utf-8, Size: 861 bytes --]
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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Ç+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2009-06-06 0:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 18:26 [BUILD FAILURE 01/04] Next June 04:PPC64 randconfig [drivers/staging/comedi/drivers.o] Subrata Modak
2009-06-05 18:26 ` Greg KH
2009-06-05 23:31 ` Benjamin Herrenschmidt
2009-06-05 23:32 ` Benjamin Herrenschmidt
2009-06-06 0:56 ` David Miller [this message]
2009-06-06 4:16 ` Benjamin Herrenschmidt
2009-06-06 5:51 ` Greg KH
2009-06-06 13:36 ` Frank Mori Hess
2009-06-07 14:36 ` Subrata Modak
2009-06-09 3:50 ` Benjamin Herrenschmidt
2009-06-09 18:34 ` Subrata Modak
2009-06-09 18:54 ` Geert Uytterhoeven
2009-06-09 22:34 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2009-06-04 13:31 Subrata Modak
2009-06-04 18:07 ` Greg KH
2009-06-04 20:40 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090605.175656.95336229.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sachinp@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=subrata@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox