Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2128573yba; Wed, 3 Apr 2019 01:46:03 -0700 (PDT) X-Google-Smtp-Source: APXvYqwlTUlQ/09WgLNdO+CQvI73RFa2NLy45Szcfd9vYrtL05Zqv2VAzHlsCydfJgcfb2hbCQvd X-Received: by 2002:a63:cf11:: with SMTP id j17mr71919496pgg.252.1554281162945; Wed, 03 Apr 2019 01:46:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554281162; cv=none; d=google.com; s=arc-20160816; b=hC7wPHWaw0ldvywR6k3xIblZ3gaMX/5WaXbFl8VJBnNGekk9kVrlL18AFIthnESo0D 72kmC21iHP32wWs1bx6hdcCoNUUD1XQH4TWkq/8+HsmOgJCR0fDxYjqYIp87Zv4OcuJk SNK83h6JS0j8QU5vudK2duO873/Mk+Kiqo6RexvDJRR47nJUO7JkyAk5eOfEXjIfV3q7 MQIyBcTDuiqRrNDqOYXNlz4bmD0oGfMQX4F7sM2UwpyuEgQsJyiLj5jLylj0ZdFIOvEn hbyKKWzYK8PFqJpiSnWbN8Nye3Xby4VK39Y3WAl6GFKYz17kkaLwJPQoWs+q8VyIHMAz YnUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=EAEql048vzeKUcBnMgRBNvcOe50hTmDaoR6fZn19O84=; b=rIwmE5T/ccbpbFCSE1Q+2OdSnIFNNY628M3oiqBurdmwUxQ2m0YgNitKXwGbVFCAwr aKHTUMndUowcP3xHFMd45lFXfFdXKt8scvh+V9yIJrfSMiibDwxMPHdRGd8jb7/1M2Md G/dzb1B+3uy3jr3Vtx//KNHLn6tb7C9uev/d9x+gFEZEiCL6qg1rYBRPXZAiVp9PSGaw bt117AGExwL1mP4ChJqGKe62L55D+CaQUQ8YIHj6zargLTK/EpqatS5iQ7HFFH6650Pw W1RrSu9Z9sCteVm8bwl8DPcAgdexd6u84OBcOZZDgZtiploDv83hMI/0Y/1lpmkZcpAw 45+Q== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v9si12886080pgr.462.2019.04.03.01.45.47; Wed, 03 Apr 2019 01:46:02 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728645AbfDCIpO (ORCPT + 99 others); Wed, 3 Apr 2019 04:45:14 -0400 Received: from charybdis-ext.suse.de ([195.135.221.2]:41128 "EHLO suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725990AbfDCIpN (ORCPT ); Wed, 3 Apr 2019 04:45:13 -0400 Received: by suse.de (Postfix, from userid 1000) id 76BCC47E5; Wed, 3 Apr 2019 10:45:12 +0200 (CEST) Date: Wed, 3 Apr 2019 10:45:12 +0200 From: Oscar Salvador To: Anshuman Khandual Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org, akpm@linux-foundation.org, will.deacon@arm.com, catalin.marinas@arm.com, mhocko@suse.com, mgorman@techsingularity.net, james.morse@arm.com, mark.rutland@arm.com, robin.murphy@arm.com, cpandya@codeaurora.org, arunks@codeaurora.org, dan.j.williams@intel.com, logang@deltatee.com, pasha.tatashin@oracle.com, david@redhat.com, cai@lca.pw Subject: Re: [PATCH 4/6] mm/hotplug: Reorder arch_remove_memory() call in __remove_memory() Message-ID: <20190403084512.otsvifwxuycoe5dn@d104.suse.de> References: <1554265806-11501-1-git-send-email-anshuman.khandual@arm.com> <1554265806-11501-5-git-send-email-anshuman.khandual@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1554265806-11501-5-git-send-email-anshuman.khandual@arm.com> User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 03, 2019 at 10:00:04AM +0530, Anshuman Khandual wrote: > Re-ordering arch_remove_memory() with memblock_[free|remove] solves the > problem on arm64 as pfn_valid() behaves correctly and returns positive > as memblock for the address range still exists. arch_remove_memory() > removes applicable memory sections from zone with __remove_pages() and > tears down kernel linear mapping. Removing memblock regions afterwards > is consistent. > > Signed-off-by: Anshuman Khandual Yes, I cannot see a way of those two colliding with each other, and a testing on my box did not raise anything spooky either. Reviewed-by: Oscar Salvador > --- > mm/memory_hotplug.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c > index 0082d69..71d0d79 100644 > --- a/mm/memory_hotplug.c > +++ b/mm/memory_hotplug.c > @@ -1872,11 +1872,10 @@ void __ref __remove_memory(int nid, u64 start, u64 size) > > /* remove memmap entry */ > firmware_map_remove(start, start + size, "System RAM"); > + arch_remove_memory(nid, start, size, NULL); > memblock_free(start, size); > memblock_remove(start, size); > > - arch_remove_memory(nid, start, size, NULL); > - > try_offline_node(nid); > > mem_hotplug_done(); > -- > 2.7.4 > -- Oscar Salvador SUSE L3