Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754460AbbGXQe3 (ORCPT ); Fri, 24 Jul 2015 12:34:29 -0400 Received: from eu-smtp-delivery-143.mimecast.com ([207.82.80.143]:17034 "EHLO eu-smtp-delivery-143.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752506AbbGXQe2 convert rfc822-to-8bit (ORCPT ); Fri, 24 Jul 2015 12:34:28 -0400 Date: Fri, 24 Jul 2015 17:34:25 +0100 From: Catalin Marinas To: Will Deacon Cc: "Jonathan (Zhixiong) Zhang" , "fu.wei@linaro.org" , "al.stone@linaro.org" , "bp @ alien8 . de Matt Fleming" , "rjw@rjwysocki.net" , "linux-kernel@vger.kernel.org" , "linaro-acpi@lists.linaro.org" Subject: Re: [PATCH V7 3/5] arm64: mm: add PROT_DEVICE_nGnRnE and PROT_NORMAL_WT Message-ID: <20150724163425.GY3550@e104818-lin.cambridge.arm.com> References: <1437515960-16812-1-git-send-email-zjzhang@codeaurora.org> <1437515960-16812-4-git-send-email-zjzhang@codeaurora.org> <20150724161500.GV3550@e104818-lin.cambridge.arm.com> <20150724162654.GB21177@arm.com> MIME-Version: 1.0 In-Reply-To: <20150724162654.GB21177@arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-OriginalArrivalTime: 24 Jul 2015 16:34:25.0636 (UTC) FILETIME=[9A7C0A40:01D0C62E] X-MC-Unique: lxmyPakoRBCWVoihBfvR9A-1 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1004 Lines: 28 On Fri, Jul 24, 2015 at 05:26:54PM +0100, Will Deacon wrote: > On Fri, Jul 24, 2015 at 05:15:00PM +0100, Catalin Marinas wrote: > > On Tue, Jul 21, 2015 at 10:59:18PM +0100, Jonathan (Zhixiong) Zhang wrote: > > > * > > > * n = AttrIndx[2:0] > > > * n MAIR > > > @@ -303,12 +303,14 @@ ENTRY(__cpu_setup) > > > * DEVICE_GRE 010 00001100 > > > * NORMAL_NC 011 01000100 > > > * NORMAL 100 11111111 > > > + * NORMAL_WT 101 10111011 > > > > I don't think the write allocation hint makes much sense for WT memory > > (though it shouldn't cause issues either). Just use 10101010. > > The EFI spec actually specifies the 1011 1011 encoding, so I think we should > follow that. OK (I didn't bother reading the spec). -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/