From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: [RFC 2/3] arm: mm: Define set_memory_* functions for ARM Date: Wed, 12 Jun 2013 18:32:38 +0100 Message-ID: <20130612173238.GV18614@n2100.arm.linux.org.uk> References: <1371057810-3189-1-git-send-email-lauraa@codeaurora.org> <1371057810-3189-3-git-send-email-lauraa@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1371057810-3189-3-git-send-email-lauraa@codeaurora.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Laura Abbott Cc: Nicoas Pitre , Catalin Marinas , Will Deacon , linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org On Wed, Jun 12, 2013 at 10:23:29AM -0700, Laura Abbott wrote: > Other architectures define various set_memory functions to allow > attributes to be changed (e.g. set_memory_x, set_memory_rw, etc.) > Currently, these functions are missing on ARM. Define these in an > appropriate manner for ARM. Please ensure that these functions only accept arguments for the module range; they will fail probably very noisily and destructively if they encounter the section mappings which we use for the direct RAM mapping.