From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752471AbaBNTbX (ORCPT ); Fri, 14 Feb 2014 14:31:23 -0500 Received: from mail-oa0-f50.google.com ([209.85.219.50]:49615 "EHLO mail-oa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751772AbaBNTbV (ORCPT ); Fri, 14 Feb 2014 14:31:21 -0500 MIME-Version: 1.0 In-Reply-To: <20140214192322.GJ30257@n2100.arm.linux.org.uk> References: <20140213195230.GA15275@www.outflux.net> <20140214101724.GC10590@arm.com> <20140214192322.GJ30257@n2100.arm.linux.org.uk> Date: Fri, 14 Feb 2014 11:31:21 -0800 X-Google-Sender-Auth: EdOs1EdR78r7eUa_HXUKRLi-hy0 Message-ID: Subject: Re: [PATCH v3] ARM: mm: report both sections from PMD From: Kees Cook To: Russell King - ARM Linux Cc: Catalin Marinas , Steve Capper , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 14, 2014 at 11:23 AM, Russell King - ARM Linux wrote: >> https://lkml.org/lkml/2014/2/12/662 > > It's not that simple, because APX in section descriptors doesn't exist > on pre-v6 ARMs. This needs to be conditional upon the CPU arch. Ah! Okay, do we need a single #define to describe the expected masks and values? What should it look like for pre-v6 ARMs? -Kees -- Kees Cook Chrome OS Security From mboxrd@z Thu Jan 1 00:00:00 1970 From: keescook@chromium.org (Kees Cook) Date: Fri, 14 Feb 2014 11:31:21 -0800 Subject: [PATCH v3] ARM: mm: report both sections from PMD In-Reply-To: <20140214192322.GJ30257@n2100.arm.linux.org.uk> References: <20140213195230.GA15275@www.outflux.net> <20140214101724.GC10590@arm.com> <20140214192322.GJ30257@n2100.arm.linux.org.uk> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Feb 14, 2014 at 11:23 AM, Russell King - ARM Linux wrote: >> https://lkml.org/lkml/2014/2/12/662 > > It's not that simple, because APX in section descriptors doesn't exist > on pre-v6 ARMs. This needs to be conditional upon the CPU arch. Ah! Okay, do we need a single #define to describe the expected masks and values? What should it look like for pre-v6 ARMs? -Kees -- Kees Cook Chrome OS Security