From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail203.messagelabs.com (mail203.messagelabs.com [216.82.254.243]) by kanga.kvack.org (Postfix) with ESMTP id 851056B0087 for ; Tue, 4 Jan 2011 11:59:05 -0500 (EST) Received: by eyh6 with SMTP id 6so3470764eyh.14 for ; Tue, 04 Jan 2011 08:59:02 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <20101223100642.GD3636@n2100.arm.linux.org.uk> Date: Tue, 4 Jan 2011 17:59:01 +0100 Message-ID: Subject: Re: [PATCHv8 00/12] Contiguous Memory Allocator From: =?UTF-8?Q?Micha=C5=82_Nazarewicz?= Content-Type: text/plain; charset=UTF-8 Sender: owner-linux-mm@kvack.org To: Johan MOSSBERG Cc: Russell King - ARM Linux , Kyungmin Park , "linux-arm-kernel@lists.infradead.org" , Daniel Walker , Mel Gorman , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , Ankita Garg , Andrew Morton , "linux-media@vger.kernel.org" , KAMEZAWA Hiroyuki , Marek Szyprowski List-ID: > Russell King wrote: >> Has anyone addressed my issue with it that this is wide-open for >> abuse by allocating large chunks of memory, and then remapping >> them in some way with different attributes, thereby violating the >> ARM architecture specification? 2011/1/4 Johan MOSSBERG : > Where in the specification (preferably ARMv7) can I find > information about this? Is the problem that it is simply > forbidden to map an address multiple times with different cache > setting and if this is done the hardware might start failing? Or > is the problem that having an address mapped cached means that > speculative pre-fetch can read it into the cache at any time, > possibly causing problems if an un-cached mapping exists? IIRC both apply. -- 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/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: email@kvack.org