Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp2802624imc; Wed, 13 Mar 2019 01:30:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqx8NKNGSffTFdv7OaRr1ep2ZvF/kk3YDz+0g/bDoaT9KNrkojbIRlkFrtO0wC1q+IQL906K X-Received: by 2002:a65:63c2:: with SMTP id n2mr39012222pgv.439.1552465815975; Wed, 13 Mar 2019 01:30:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552465815; cv=none; d=google.com; s=arc-20160816; b=FfKrREE+556fqp+dqJMXhng52jy2jUgxS3xYhqG9JvneyvzkRMYME07KIazdqj147x 6g+rORcfv5rIlC4aMDDkGFx3SnauHXLsT7IHqidJAmUUWHMy2RrCM5gZJRMjrUFDGY7o maQ7ldkexnyKLlStIeNUqTn67mVVqOqZbI2ks4bieg9dGyUHlWc/hq8govRFe8u4R7Hs k5yiq1bjP9hmvZiNZ4G95PvLzeRZdkf4dYRXwBgaINbcvg3MJeFWvVnKuJK3odvSy5ay yBZVr562MgxvuvJQ4lQ1KMVtdTLptvtw6p2la26I6IAhSMpNT1/IqagliUFDuVpia230 wyqg== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=W4K8HqPdmHDoyszFoA1g1FpkOszyeUQWUM9XwTCGzlQ=; b=AfkRj6dOmaIlt2nL0AOkeMxCyNWw15WYwzWUV4uloml1mnepaQMPCI03Hw54bkG+4t wgUctDKd1ZrJTvAXtvO0SNY/D0xKOGJT8UgSRxzshnkTIuUyowpyAgQwfhqn0w4uVkMf wBPhQJizZ+RDIw/wRjAKwCARg3ZZSvyafxUWKUuLVt8DxtN2QmEHf74+1S6pz3iWsnjm QOpiZbcSFlKmzz7KIs/TsgjitKraHx/2LHApXo7qIieXTRTW/wU7qC+oKFH2dbo3s+Db E4TiVLdtSxYQnEXFMQ2GJ0yNBO2I6Y1lR4UBtdwUwMNbFeTZVvFHKoaVxqntR/6HbytQ FgAQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@c-s.fr header.s=mail header.b=Eea3DG5e; 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 gn14si10257766plb.171.2019.03.13.01.29.59; Wed, 13 Mar 2019 01:30:15 -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=@c-s.fr header.s=mail header.b=Eea3DG5e; 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 S1727175AbfCMI2n (ORCPT + 99 others); Wed, 13 Mar 2019 04:28:43 -0400 Received: from pegase1.c-s.fr ([93.17.236.30]:13206 "EHLO pegase1.c-s.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726629AbfCMI2n (ORCPT ); Wed, 13 Mar 2019 04:28:43 -0400 Received: from localhost (mailhub1-int [192.168.12.234]) by localhost (Postfix) with ESMTP id 44K4k00bp9z9tyrK; Wed, 13 Mar 2019 09:28:40 +0100 (CET) Authentication-Results: localhost; dkim=pass reason="1024-bit key; insecure key" header.d=c-s.fr header.i=@c-s.fr header.b=Eea3DG5e; dkim-adsp=pass; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at c-s.fr Received: from pegase1.c-s.fr ([192.168.12.234]) by localhost (pegase1.c-s.fr [192.168.12.234]) (amavisd-new, port 10024) with ESMTP id 2MO69eW5V_GA; Wed, 13 Mar 2019 09:28:40 +0100 (CET) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase1.c-s.fr (Postfix) with ESMTP id 44K4jz6Qzcz9tyrD; Wed, 13 Mar 2019 09:28:39 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c-s.fr; s=mail; t=1552465719; bh=W4K8HqPdmHDoyszFoA1g1FpkOszyeUQWUM9XwTCGzlQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Eea3DG5e0dXFTOI9anDheYtALfiSEt/FIuN3uv4+fF8sNt4SGwPDAgqgZp9K5oACm 5Tk6QT+bqRBcRLZV7Kdoig6I/G/W3CFyJawgUOf5OSkhLiPMMFhcxQ/8PUmO9I5FbA qUT+lzy785k18YpOqSGrsjNjj555FLJAI6HnWKTM= Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id C354E8B8F5; Wed, 13 Mar 2019 09:28:40 +0100 (CET) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id HLhckdp2oziU; Wed, 13 Mar 2019 09:28:40 +0100 (CET) Received: from PO15451 (unknown [192.168.4.90]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 06C108B8EE; Wed, 13 Mar 2019 09:28:39 +0100 (CET) Subject: Re: [PATCH v2] powerpc/mm: move warning from resize_hpt_for_hotplug() To: Laurent Vivier , linux-kernel@vger.kernel.org Cc: Michael Ellerman , linuxppc-dev@lists.ozlabs.org, David Gibson References: <20190308105413.4302-1-lvivier@redhat.com> <3db6b64d-02d3-8aa7-80ca-3e469ea743ff@c-s.fr> <1dfe1a2e-f6f9-2d5d-a38e-ba4517794bad@redhat.com> From: Christophe Leroy Message-ID: <6f089371-29e6-6fa9-379d-76d3a87e2b8b@c-s.fr> Date: Wed, 13 Mar 2019 09:28:39 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: <1dfe1a2e-f6f9-2d5d-a38e-ba4517794bad@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 13/03/2019 à 09:01, Laurent Vivier a écrit : > On 13/03/2019 07:03, Christophe Leroy wrote: >> >> >> Le 08/03/2019 à 11:54, Laurent Vivier a écrit : >>> resize_hpt_for_hotplug() reports a warning when it cannot >>> resize the hash page table ("Unable to resize hash page >>> table to target order") but in some cases it's not a problem >>> and can make user thinks something has not worked properly. >>> >>> This patch moves the warning to arch_remove_memory() to >>> only report the problem when it is needed. >>> >>> Signed-off-by: Laurent Vivier >>> --- >>>   arch/powerpc/include/asm/sparsemem.h  |  4 ++-- >>>   arch/powerpc/mm/hash_utils_64.c       | 17 ++++++----------- >>>   arch/powerpc/mm/mem.c                 |  3 ++- >>>   arch/powerpc/platforms/pseries/lpar.c |  3 ++- >>>   4 files changed, 12 insertions(+), 15 deletions(-) >>> >>> diff --git a/arch/powerpc/include/asm/sparsemem.h >>> b/arch/powerpc/include/asm/sparsemem.h >>> index 68da49320592..3192d454a733 100644 >>> --- a/arch/powerpc/include/asm/sparsemem.h >>> +++ b/arch/powerpc/include/asm/sparsemem.h >>> @@ -17,9 +17,9 @@ extern int create_section_mapping(unsigned long >>> start, unsigned long end, int ni >>>   extern int remove_section_mapping(unsigned long start, unsigned long >>> end); >>>     #ifdef CONFIG_PPC_BOOK3S_64 >>> -extern void resize_hpt_for_hotplug(unsigned long new_mem_size); >>> +extern int resize_hpt_for_hotplug(unsigned long new_mem_size); >>>   #else >>> -static inline void resize_hpt_for_hotplug(unsigned long new_mem_size) >>> { } >>> +static inline int resize_hpt_for_hotplug(unsigned long new_mem_size) >>> { return 0; } >>>   #endif >>>     #ifdef CONFIG_NUMA >>> diff --git a/arch/powerpc/mm/hash_utils_64.c >>> b/arch/powerpc/mm/hash_utils_64.c >>> index 0cc7fbc3bd1c..40bb2a8326bb 100644 >>> --- a/arch/powerpc/mm/hash_utils_64.c >>> +++ b/arch/powerpc/mm/hash_utils_64.c >>> @@ -755,12 +755,12 @@ static unsigned long __init >>> htab_get_table_size(void) >>>   } >>>     #ifdef CONFIG_MEMORY_HOTPLUG >>> -void resize_hpt_for_hotplug(unsigned long new_mem_size) >>> +int resize_hpt_for_hotplug(unsigned long new_mem_size) >>>   { >>>       unsigned target_hpt_shift; >>>         if (!mmu_hash_ops.resize_hpt) >>> -        return; >>> +        return 0; >>>         target_hpt_shift = htab_shift_for_mem_size(new_mem_size); >>>   @@ -773,15 +773,10 @@ void resize_hpt_for_hotplug(unsigned long >>> new_mem_size) >>>        * current shift >>>        */ >>>       if ((target_hpt_shift > ppc64_pft_size) >>> -        || (target_hpt_shift < (ppc64_pft_size - 1))) { >>> -        int rc; >>> - >>> -        rc = mmu_hash_ops.resize_hpt(target_hpt_shift); >>> -        if (rc && (rc != -ENODEV)) >>> -            printk(KERN_WARNING >>> -                   "Unable to resize hash page table to target order >>> %d: %d\n", >>> -                   target_hpt_shift, rc); >>> -    } >>> +        || (target_hpt_shift < (ppc64_pft_size - 1))) >> >> The || should go on the line above and the two (target_hpt... should be >> aligned, and the () after the < are superflous. >> >> And indeed, we should (in another patch) rename 'target_hpt_shift' with >> a shorter name, this would avoid multiple lines. >> >> Ref >> https://www.kernel.org/doc/html/latest/process/coding-style.html#naming : >> >> LOCAL variable names should be short, and to the point. If you have some >> random integer loop counter, it should probably be called i. Calling it >> loop_counter is non-productive, if there is no chance of it being >> mis-understood. Similarly, tmp can be just about any type of variable >> that is used to hold a temporary value. >> >> If you are afraid to mix up your local variable names, you have another >> problem, which is called the function-growth-hormone-imbalance syndrome. >> See chapter 6 (Functions). >> > > I'm only removing a warning. Do we really need to rewrite all the code > around for that? No, and that's the reason why I said it could be done in another (future) patch. Anyway, your patch should be clean regarding checkpatch See https://patchwork.ozlabs.org/patch/1052984/ And https://openpower.xyz/job/snowpatch/job/snowpatch-linux-checkpatch/3298//artifact/linux/checkpatch.log CHECK:AVOID_EXTERNS: extern prototypes should be avoided in .h files #31: FILE: arch/powerpc/include/asm/sparsemem.h:20: +extern int resize_hpt_for_hotplug(unsigned long new_mem_size); CHECK:LOGICAL_CONTINUATIONS: Logical continuations should be on the previous line #70: FILE: arch/powerpc/mm/hash_utils_64.c:776: if ((target_hpt_shift > ppc64_pft_size) + || (target_hpt_shift < (ppc64_pft_size - 1))) total: 0 errors, 0 warnings, 2 checks, 60 lines checked NOTE: For some of the reported defects, checkpatch may be able to mechanically convert to the typical style using --fix or --fix-inplace. the.patch has style problems, please review. NOTE: Ignored message types: ARCH_INCLUDE_LINUX BIT_MACRO COMPARISON_TO_NULL DT_SPLIT_BINDING_PATCH EMAIL_SUBJECT FILE_PATH_CHANGES GLOBAL_INITIALISERS LINE_SPACING MULTIPLE_ASSIGNMENTS NOTE: If any of the errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS. Christophe > > Thanks, > Laurent >