Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1128954yba; Thu, 4 Apr 2019 04:59:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqwBn93juQDVw1mrmnF9MBynFoGSvu/V+7aZZ4t7YXwq8BKQjPoqEMfy7vCzFZwdkT39RQBX X-Received: by 2002:a17:902:778a:: with SMTP id o10mr5954604pll.135.1554379152524; Thu, 04 Apr 2019 04:59:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554379152; cv=none; d=google.com; s=arc-20160816; b=vOAUKfS0J2uhwJlXiblva2K9IUMUJ3IIhnSrbJH1WCPj15uxO/jOJOGnzfh6wbLGPU 368sEd319KjjJGI/VRYxoFHsqW4lnjqG7gxv+kpzna6TiaNMXOMp4HCzG/ShzPTPsSag Fnav7uYyPjjco6kISZZ0WcWWwPmN2oYp75au0egTTQ2tIWh+/JZs0R0TzR3ZMLXZ/qbf ZWK7gYnHSiIYY6t347uxkbKumpZlr+KL9KVjiojhARxWdcNpDClfzY6NPf4ZAaaK9hmg irqYIHMpIXXYPtLr0FsTraB6tGBA6Sa01ar+GGDXz39hjmk+Ir3vGxydHUZ5ekjSyr6s 0oAw== 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=f/Hp9t9XbVD5bSZKUK76GFPnShqv18BolclV2d36SZI=; b=Shwl+Qbnz9f9nvvZ0OwbCrvFcP8LK7lBAHR/uSUZ1kGV147mKN1nx5/aV28JyjHJaU asoF83tYdw6PVk3lR/XOC3LUMAoVH29PUVm80ClMinhj7T5lJnkFqpyx/mpD3Pae9VJC GE3oPllzrvkxOVp8MwaKgz4ybx+EXoz8MBa3MBkEWfzo18st507bSA5p1SCrNBGRoP70 KYVjkRdmetZC/2aeK37Q3xEfPhsHhmquSkH+hRe5h9NXMMJCPswPxFReZQ56D5PmPWOH xGHQ8h0YmMMMvUbWIc5b3Re7hqAmRhHkQiaLd0Zx2/aJ7uRCC+tXxmQKqsRtkYfDgQ4Z kqTg== 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 d8si14058711plo.157.2019.04.04.04.58.56; Thu, 04 Apr 2019 04:59:12 -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 S1729319AbfDDL6U (ORCPT + 99 others); Thu, 4 Apr 2019 07:58:20 -0400 Received: from nat.nue.novell.com ([195.135.221.2]:34277 "EHLO suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727039AbfDDL6T (ORCPT ); Thu, 4 Apr 2019 07:58:19 -0400 Received: by suse.de (Postfix, from userid 1000) id BC97B4812; Thu, 4 Apr 2019 13:58:18 +0200 (CEST) Date: Thu, 4 Apr 2019 13:58:18 +0200 From: Oscar Salvador To: Anshuman Khandual Cc: Robin Murphy , 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, cpandya@codeaurora.org, arunks@codeaurora.org, dan.j.williams@intel.com, logang@deltatee.com, pasha.tatashin@oracle.com, david@redhat.com, cai@lca.pw, Steven Price Subject: Re: [PATCH 2/6] arm64/mm: Enable memory hot remove Message-ID: <20190404115815.gzk3sgg34eofyxfv@d104.suse.de> References: <1554265806-11501-1-git-send-email-anshuman.khandual@arm.com> <1554265806-11501-3-git-send-email-anshuman.khandual@arm.com> <55278a57-39bc-be27-5999-81d0da37b746@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55278a57-39bc-be27-5999-81d0da37b746@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 Thu, Apr 04, 2019 at 11:09:22AM +0530, Anshuman Khandual wrote: > > Do these need to be __meminit? AFAICS it's effectively redundant with the containing #ifdef, and removal feels like it's inherently a later-than-init thing anyway. > > I was confused here a bit but even X86 does exactly the same. All these functions > are still labeled __meminit and all wrapped under CONFIG_MEMORY_HOTPLUG. Is there > any concern to have __meminit here ? We do not really need it as long as the code is within #ifdef CONFIG_MEMORY_HOTPLUG. __meminit is being used when functions that are going to be need for hotplug need to stay around. /* Used for MEMORY_HOTPLUG */ #define __meminit __section(.meminit.text) __cold notrace \ __latent_entropy #if defined(CONFIG_MEMORY_HOTPLUG) #define MEM_KEEP(sec) *(.mem##sec) #define MEM_DISCARD(sec) #else #define MEM_KEEP(sec) #define MEM_DISCARD(sec) *(.mem##sec) #endif So it is kind of redundant to have both. I will clean it up when reposting [1] and [2]. [1] https://patchwork.kernel.org/patch/10875019/ [2] https://patchwork.kernel.org/patch/10875021/ -- Oscar Salvador SUSE L3