[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinjd6_X62XPAvHNK4Tf233yD0-LKBBe96CE8_T2@mail.gmail.com>
Date: Fri, 15 Oct 2010 17:25:07 +0300
From: Felipe Contreras <felipe.contreras@...il.com>
To: linux-main <linux-kernel@...r.kernel.org>,
linux-arm <linux-arm-kernel@...ts.infradead.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Catalin Marinas <catalin.marinas@....com>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Russell King <linux@....linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Richard Woodruff <r-woodruff2@...com>,
Felipe Contreras <felipe.contreras@...il.com>
Subject: Re: [PATCH .36-rc8] arm: mm: allow, but warn, when issuing ioremap()
on RAM
On Fri, Oct 15, 2010 at 5:15 PM, Felipe Contreras
<felipe.contreras@...il.com> wrote:
> From: Catalin Marinas <catalin.marinas@....com>
>
> Drivers have been relying on this behavior, but done so wrongly.
> However, rather than breaking drivers from .35 to .36, we should warn on
> .36 and only break on .37. This way we give a chance for contributors to
> fix the issues.
>
> According to ARM, the behavior of having multiple mappings is
> unspecified from ARMv6+. This causes real issues specially on modern
> hardware, and specially with speculative prefetching. So drivers need to
> be fixed.
>
> Also, since current hardware has palliative meassures to deal with
> multiple mappings with the same memory type but diferent cacheability
> attributes, ensure that such restriction is taking place.
Ah, disregard this, a similar one is on .36-rc8 already (06c1088), I
wasn't CC'ed.
--
Felipe Contreras
--
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/
Powered by blists - more mailing lists