From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id EE82DA04 for ; Mon, 6 Jul 2015 22:04:50 +0000 (UTC) Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8F09DFB for ; Mon, 6 Jul 2015 22:04:50 +0000 (UTC) Message-ID: <1436220279.3948.75.camel@kernel.crashing.org> From: Benjamin Herrenschmidt To: Andy Lutomirski Date: Tue, 07 Jul 2015 08:04:39 +1000 In-Reply-To: References: <1435997837.3948.21.camel@kernel.crashing.org> <1436065368.3948.48.camel@kernel.crashing.org> <20150706095256.GA27723@e104818-lin.cambridge.arm.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: "ksummit-discuss@lists.linuxfoundation.org" Subject: Re: [Ksummit-discuss] [TECH TOPIC] Semantics of MMIO mapping attributes accross archs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2015-07-06 at 10:14 -0700, Andy Lutomirski wrote: > I should have said it more clearly: I think that this construct > *should* result in the outermost prot. That is: pgprot_xyz(p) should > have mode xyz regardless of p. > > x86 doesn't work that way right now. Instead pgprot_xyz(p) returns > garbage if p has prot bits set. Agreed. It should. Ben.