From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot0-f199.google.com (mail-ot0-f199.google.com [74.125.82.199]) by kanga.kvack.org (Postfix) with ESMTP id 108E46B0038 for ; Sat, 18 Nov 2017 08:48:56 -0500 (EST) Received: by mail-ot0-f199.google.com with SMTP id e5so2761371otj.14 for ; Sat, 18 Nov 2017 05:48:56 -0800 (PST) Received: from foss.arm.com (usa-sjc-mx-foss1.foss.arm.com. [217.140.101.70]) by mx.google.com with ESMTP id n16si2182231otd.535.2017.11.18.05.48.54 for ; Sat, 18 Nov 2017 05:48:54 -0800 (PST) Date: Sat, 18 Nov 2017 13:48:41 +0000 From: Marc Zyngier Subject: Re: [PATCH 01/11] Initialize the mapping of KASan shadow memory Message-ID: <20171118134841.3f6c9183@why.wild-wind.fr.eu.org> In-Reply-To: References: <8e959f69-a578-793b-6c32-18b5b0cd08c2@arm.com> <87a7znsubp.fsf@on-the-bus.cambridge.arm.com> <87po8ir1kg.fsf@on-the-bus.cambridge.arm.com> <87375eqobb.fsf@on-the-bus.cambridge.arm.com> <20171117073556.GB28855@cbox> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: "Liuwenliang (Abbott Liu)" Cc: Christoffer Dall , "linux@armlinux.org.uk" , "aryabinin@virtuozzo.com" , "afzal.mohd.ma@gmail.com" , "f.fainelli@gmail.com" , "labbott@redhat.com" , "kirill.shutemov@linux.intel.com" , "mhocko@suse.com" , "catalin.marinas@arm.com" , "akpm@linux-foundation.org" , "mawilcox@microsoft.com" , "tglx@linutronix.de" , "thgarnie@google.com" , "keescook@chromium.org" , "arnd@arndb.de" , "vladimir.murzin@arm.com" , "tixy@linaro.org" , "ard.biesheuvel@linaro.org" , "robin.murphy@arm.com" , "mingo@kernel.org" , "grygorii.strashko@linaro.org" , "glider@google.com" , "dvyukov@google.com" , "opendmb@gmail.com" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "kasan-dev@googlegroups.com" , "linux-mm@kvack.org" , Jiazhenghua , Dailei , Zengweilin , Heshaoliang On Sat, 18 Nov 2017 10:40:08 +0000 "Liuwenliang (Abbott Liu)" wrote: > On Nov 17, 2017 15:36 Christoffer Dall [mailto:cdall@linaro.org] wrote: > >If your processor does support LPAE (like a Cortex-A15 for example), > >then you have both the 32-bit accessors (MRC and MCR) and the 64-bit > >accessors (MRRC, MCRR), and using the 32-bit accessor will simply access > >the lower 32-bits of the 64-bit register. > > > >Hope this helps, > >-Christoffer > > If you know the higher 32-bits of the 64-bits cp15's register is not useful for your system, > then you can use the 32-bit accessor to get or set the 64-bit cp15's register. > But if the higher 32-bits of the 64-bits cp15's register is useful for your system, > then you can't use the 32-bit accessor to get or set the 64-bit cp15's register. > > TTBR0/TTBR1/PAR's higher 32-bits is useful for CPU supporting LPAE. > The following description which comes from ARM(r) Architecture Reference > Manual ARMv7-A and ARMv7-R edition tell us the reason: > > 64-bit TTBR0 and TTBR1 format: > ... > BADDR, bits[39:x] : > Translation table base address, bits[39:x]. Defining the translation table base address width on > page B4-1698 describes how x is defined. > The value of x determines the required alignment of the translation table, which must be aligned to > 2x bytes. > > Abbott Liu: Because BADDR on CPU supporting LPAE may be bigger than max value of 32-bit, so bits[39:32] may > be valid value which is useful for the system. > > 64-bit PAR format > ... > PA[39:12] > Physical Address. The physical address corresponding to the supplied virtual address. This field > returns address bits[39:12]. > > Abbott Liu: Because Physical Address on CPU supporting LPAE may be bigger than max value of 32-bit, > so bits[39:32] may be valid value which is useful for the system. > > Conclusion: Don't use 32-bit accessor to get or set TTBR0/TTBR1/PAR on CPU supporting LPAE, > if you do that, your system may run error. That's not really true. You can run an non-LPAE kernel that uses the 32bit accessors an a Cortex-A15 that supports LPAE. You're just limited to 4GB of physical space. And you're pretty much guaranteed to have some memory below 4GB (one way or another), or you'd have a slight problem setting up your page tables. M. -- Without deviation from the norm, progress is not possible. -- 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/ . Don't email: email@kvack.org