Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp302109pxb; Wed, 11 Nov 2020 04:11:59 -0800 (PST) X-Google-Smtp-Source: ABdhPJyGKjs4ZuBXef1rqH3L9pHiI3zZ3BgLR7pOxchJV41m85Cx9Fp+9SZZMzLaUzaVk8bIi/VT X-Received: by 2002:aa7:c713:: with SMTP id i19mr25520163edq.296.1605096719000; Wed, 11 Nov 2020 04:11:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605096718; cv=none; d=google.com; s=arc-20160816; b=vRCUmPTSbqxT0cRKJhl1XMlPx5PfIAxWRXbtvEByEbFeEsoI0f4giuBkBPShVsSxPO +rCEvD7RkB0d+n6QQzJvV6o445MQQ4wMtbHbjdcS37jNLj5jVtsE4km80DkHcve2xQ8H gYW+HRalUGhUwx9ZQ3p7hGl5xhSN6uYGP1JbyQEP7RwjlouwonUbDqp2Xr6Mi88gAhS0 wswLUWeJVMKFLMGhmclmnjNiZ4pQdgeZAkdc28llCifBrB1W/Ab670Oco858ZQ9xGAoE ytZOLqgDQ/mXBkHrLoDpTgcsfUwhkuSNX7cbSaTRTWpXBIYW4aNLfuppokuUmUXVTHYb BRGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:organization :from:references:cc:to:subject:dkim-signature; bh=g28Vcy6bkD9hVBLAqs39T3DMq7VTyzZfkpQarBjwdtM=; b=Rq/Ni6OvpmTSaQsNBjQT5Lb5ME0jNK0VW+rS0kS4JqxS9f8me9ji96nMBxI2X35ydp fgE20V+jRyW77aDpamOV+xSlMy+21dyshcS0NvV2G46F84pgKe1QGBYJaNyxyZXqGHDc FPJlxgsPM8leKMO11OraA0BT+h9cOHg7csh2fO8EnhsqQG4mr41zIdqVU7gvDOKkBRXl PIixhdVA0IjVbhtgh4ygu6Bwdt0vpsFbdldZZV0qvawdhrw9YdIz5dKffkFQA9kdNx2a NgZVpdYN2yHDqcTbOQxT/1A5tGmjcuUoCeUjDUvfOMIadGYLFfowXREZX3vu46OnvsFz Pr3g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=jERxhF2u; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id lz21si1214705ejb.16.2020.11.11.04.11.35; Wed, 11 Nov 2020 04:11:58 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=jERxhF2u; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725859AbgKKMIc (ORCPT + 99 others); Wed, 11 Nov 2020 07:08:32 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:53422 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726039AbgKKMH5 (ORCPT ); Wed, 11 Nov 2020 07:07:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1605096475; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=g28Vcy6bkD9hVBLAqs39T3DMq7VTyzZfkpQarBjwdtM=; b=jERxhF2u4odRUUEWmLLZ3AW+9PWNivV8JSrrpMnbeVquKcrP8H1dOxEMqjNpuEhNwDWQQo 5LmBGzzWFo+4aX7Wk9VquBC7rzGTqKuOHoh6yGSJ5FwuGLcq0vREJdJ850lu/7S1wEhVww g4HK2YgoFquhdoBymqM+6mepUnGOWOw= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-38-QKWvvqh9Nw6dyn1L5bqNgQ-1; Wed, 11 Nov 2020 07:07:51 -0500 X-MC-Unique: QKWvvqh9Nw6dyn1L5bqNgQ-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 73BE6809DE6; Wed, 11 Nov 2020 12:07:49 +0000 (UTC) Received: from [10.36.114.151] (ovpn-114-151.ams2.redhat.com [10.36.114.151]) by smtp.corp.redhat.com (Postfix) with ESMTP id 767745C1C4; Wed, 11 Nov 2020 12:07:45 +0000 (UTC) Subject: Re: [PATCH v1 3/4] powerpc/mm: remove linear mapping if __add_pages() fails in arch_add_memory() To: Oscar Salvador , Mike Rapoport Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org, Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , Rashmica Gupta , Andrew Morton , Michal Hocko , Wei Yang References: <20201029162718.29910-1-david@redhat.com> <20201029162718.29910-4-david@redhat.com> <20201104095007.GB4981@localhost.localdomain> <20201104120651.GQ4879@kernel.org> <20201104121109.GA5126@localhost.localdomain> From: David Hildenbrand Organization: Red Hat GmbH Message-ID: <4fd8b15c-3cbf-0016-69a8-235883c0bc46@redhat.com> Date: Wed, 11 Nov 2020 13:07:44 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20201104121109.GA5126@localhost.localdomain> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04.11.20 13:11, Oscar Salvador wrote: > On Wed, Nov 04, 2020 at 02:06:51PM +0200, Mike Rapoport wrote: >> On Wed, Nov 04, 2020 at 10:50:07AM +0100, osalvador wrote: >>> On Thu, Oct 29, 2020 at 05:27:17PM +0100, David Hildenbrand wrote: >>>> Let's revert what we did in case seomthing goes wrong and we return an >>>> error. >>> >>> Dumb question, but should not we do this for other arches as well? >> >> It seems arm64 and s390 already do that. >> x86 could have its arch_add_memory() improved though :) > > Right, I only stared at x86 and see it did not have it. > I guess we want to have all arches aligned with this. The ultimate goal would be to get rid of arch-specific arch_add_memory() implementations completely, providing arch_create_linear_mapping() / arch_remove_linear_mapping() instead (as indicated in patch #1). The x86 variant certainly needs love, but I'll keep this patch set powerpc specific, so it can go via the powerpc tree in one piece. I'll add unifying these implementations onto my todo list. Thanks! -- Thanks, David / dhildenb