Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2730159ybl; Mon, 19 Aug 2019 06:44:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqyYSPEQT0QGO0oq5JhF9P1y8FLBOgjh0mYmIXtqmXJwKnu98qd23CsW8jaFytCLI8ckjn5D X-Received: by 2002:a17:902:f301:: with SMTP id gb1mr21893803plb.249.1566222259320; Mon, 19 Aug 2019 06:44:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566222259; cv=none; d=google.com; s=arc-20160816; b=HNJSRrRlc7gQrareEUYVuxoLFKlVHbN/u/sTkldZ7SFmhJ7Ip5/i1DTNn57BJr8Sxg O09+tkj+5Fj1QAnFCAXt1M5+bQmuDKMEq+VkJxg5TLNAhPJlM8zckwTNbBedk50YokzX 4rpGkbw2ehR7FERG1TBC4ZRCRIFeuqs0mvM5d6QGhjBf2LneuvGVgwhQ5sIFPa1LKwIs m7Iuz7RR/aUraQIc8R/7WYCI0WfhgpP3IIymVZOjNfefsdqaMht/bw3SYj/Z/UfWhEGd Iux1yKiYFJHvSbrbyo9xW/u4rMWBIGgG+GyVF1mVNTFm5qM3HZwmwggpsR20gDIipNE2 nBLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:message-id :user-agent:mime-version:in-reply-to:references:cc:to:subject:from :date:dkim-signature; bh=RjbLMcxR301rQtXMpcTgwA0dW/K8YBmt5+fW+awk5+E=; b=Lyum8Dodf5WR3x1nnQ+klWJ/ZycxBLtOQWF9ZI9ZTLXF34lKv6UpQYe9L+UtGu58Af 6rFwoQW1MtV/yA+32LH1yPRF3tTFnOCyWHaIqkKfA0LF2hOa3GNGLDcfMbVRGxEHxhL0 kxmzBihZbX3caCrx+a0BIh/sNIB4IylrmKL3h0mScTcHVDxVKzSfRSx8Lz5UBD+s7b0C Jtu4xPu2soCMr4NMaDwiTc2NeIbmDQnXfxEoTBYORTk1Co3zno5X+EVYLb1leRBOmEvg Wuptjlt2IhJWna3vR5apG9/kipHTnJwbXqdw3CmEGMNmmibwruKj3fLrnkENE69ClQju ZB0w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tYFXZFFl; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h69si9836198pge.543.2019.08.19.06.44.04; Mon, 19 Aug 2019 06:44:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tYFXZFFl; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727661AbfHSNmv (ORCPT + 99 others); Mon, 19 Aug 2019 09:42:51 -0400 Received: from mail-pf1-f196.google.com ([209.85.210.196]:41570 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727332AbfHSNmv (ORCPT ); Mon, 19 Aug 2019 09:42:51 -0400 Received: by mail-pf1-f196.google.com with SMTP id 196so1195839pfz.8 for ; Mon, 19 Aug 2019 06:42:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:subject:to:cc:references:in-reply-to:mime-version :user-agent:message-id:content-transfer-encoding; bh=RjbLMcxR301rQtXMpcTgwA0dW/K8YBmt5+fW+awk5+E=; b=tYFXZFFlCozav7Vs9/mMpjspNezP2YD/DBroefG0UIAcNPFVG9JQQQ7Rxqj/Zqby86 ldGz6i23RyjklvekeUwHOk3PHKT/kEfffzORWCBTrKLm7yrr+YTzsYpABEraWMIMhYI+ +eHAc7kuoP5C2YDEQMsPhbl+UL21IEyWyYB8YtEBg3LKrTkSzXO7s+ZmHpwa8P+/76Dj U049W6xuNbvAOe6NDpeVnvEUbwoHpnHq/yh0DCDpS62aqeyFiKWIMpeXrgMrAuwr4Pmf XisguPW0xxY8ZfQRMu/kYGoIEGN1wROyWbGBRricaiYnRc+VKLxUooyfalIfIRMhd48H IClw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:cc:references:in-reply-to :mime-version:user-agent:message-id:content-transfer-encoding; bh=RjbLMcxR301rQtXMpcTgwA0dW/K8YBmt5+fW+awk5+E=; b=YmNxShw4F3VMFYXmOCAYS/eqX33xDpkf53heMeNMQcIoxk1HcWLoa5SBYU8sWG6zUJ 3Qgq3IJei+Q5KOoPNDSWN9SHWx0dfl/dupKdLUgSkqe30uLpqvBc8oqCSW/tze1b9ww2 7eXYQWYtlVlQK2mtfQ7qn5KZSiPUyAyXoutMmoVCnk/O29fNRxdObXlvukiXVzNuP8lw Nn8K1sGYZ2gTRsge5GozoiLd57bn/4/kHU1tA14TKoLH/KrSS7co+UF5gkww+v2uejDx oBExvkufCWK3ZMclrjFIW20Isu70JJhhFYgmbpV0HNKHQEkkYOZAc9jq0wUELrDs834m SYNg== X-Gm-Message-State: APjAAAVxOFrmTZXbRlcZuNxXH4ZqHYfP8EXUAN9Q/UshUf08PcvK4wys J9WjXKcNve83EoRZMx30C9Y= X-Received: by 2002:a63:e14d:: with SMTP id h13mr19901841pgk.431.1566222170475; Mon, 19 Aug 2019 06:42:50 -0700 (PDT) Received: from localhost (193-116-95-121.tpgi.com.au. [193.116.95.121]) by smtp.gmail.com with ESMTPSA id v12sm13863260pgr.86.2019.08.19.06.42.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 19 Aug 2019 06:42:49 -0700 (PDT) Date: Mon, 19 Aug 2019 23:42:38 +1000 From: Nicholas Piggin Subject: Re: [PATCH v1 05/10] powerpc/mm: Do early ioremaps from top to bottom on PPC64 too. To: Benjamin Herrenschmidt , Christophe Leroy , Michael Ellerman , Paul Mackerras Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org References: <6bc35eca507359075528bc0e55938bc1ce8ee485.1565726867.git.christophe.leroy@c-s.fr> <019c5d90f7027ccff00e38a3bcd633d290f6af59.1565726867.git.christophe.leroy@c-s.fr> In-Reply-To: <019c5d90f7027ccff00e38a3bcd633d290f6af59.1565726867.git.christophe.leroy@c-s.fr> MIME-Version: 1.0 User-Agent: astroid/0.15.0 (https://github.com/astroidmail/astroid) Message-Id: <1566221500.6f5zxv68dm.astroid@bobo.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Christophe Leroy's on August 14, 2019 6:11 am: > Until vmalloc system is up and running, ioremap basically > allocates addresses at the border of the IOREMAP area. >=20 > On PPC32, addresses are allocated down from the top of the area > while on PPC64, addresses are allocated up from the base of the > area. =20 This series looks pretty good to me, but I'm not sure about this patch. It seems like quite a small divergence in terms of code, and it looks like the final result still has some ifdefs in these functions. Maybe you could just keep existing behaviour for this cleanup series so it does not risk triggering some obscure regression? Merging behaviour could be proposed at the end. Thanks, Nick =