Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753696AbcLMSoc (ORCPT ); Tue, 13 Dec 2016 13:44:32 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:34265 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752343AbcLMSob (ORCPT ); Tue, 13 Dec 2016 13:44:31 -0500 Date: Wed, 14 Dec 2016 00:14:23 +0530 From: Afzal Mohammed To: Vladimir Murzin Cc: Russell King , Arnd Bergmann , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RFC 2/2] ARM: nommu: remap exception base address to RAM Message-ID: <20161213184423.GC4629@afzalpc> References: <20161211131028.3019-1-afzal.mohd.ma@gmail.com> <20161211131255.3221-1-afzal.mohd.ma@gmail.com> <584FC18D.2050908@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <584FC18D.2050908@arm.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 903 Lines: 29 Hi, On Tue, Dec 13, 2016 at 09:38:21AM +0000, Vladimir Murzin wrote: > On 11/12/16 13:12, Afzal Mohammed wrote: > > this probably would have to be made robust so as to not cause issue on > > other v7-A's upon trying to do !MMU (this won't affect normal MMU boot), > > or specifically where security extensions are not enabled. Also effect > > of hypervisor extension also need to be considered. Please let know if > > any better ways to handle this. > You might need to check ID_PFR1 for that. Had been searching ARM ARM for this kind of a thing, thanks. > > +#ifdef CONFIG_REMAP_VECTORS_TO_RAM > > + mov r3, #CONFIG_VECTORS_BASE @ read VECTORS_BASE > ldr r3,=CONFIG_VECTORS_BASE > > would be more robust. I hit this in [1] > > [1] https://www.spinics.net/lists/arm-kernel/msg546825.html Russell suggested doing it in paging_init(), then probably assembly circus can be avoided. Regards afzal