Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1157537pxb; Fri, 21 Jan 2022 11:04:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJwfPkRMIM+I3EhOMWJJHMXze1NXU/6DQoZI9nd69QfVHxNjUAD6zT3AbK0ageldJ0qStp6N X-Received: by 2002:a63:904c:: with SMTP id a73mr3878259pge.449.1642791876714; Fri, 21 Jan 2022 11:04:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642791876; cv=none; d=google.com; s=arc-20160816; b=vIbWKwPJd5OxAkM79hl8WoTKlxhSCw4L8tkKN7nYVMTIXS9eqkqpxab5+m0KqidV6H 8zlsjkx4UQZjpaQWxZWSvEZ2aF9pOdenQzfPYdBynjf6jqcRqQpt61m89D+Ue6Ps/c7p u6gv22FdsUCZyom/hVarV0tqZa+i6ULQ6U016oZxiINsVDKILW+mosVJH5YWGSHwYbiD NzbdaHmcUE8L0c8ktnavRyLlFgxURNE3I+EwfD3dtzrQVmk3Xw2s4IxsIgFXKYHML9GL /ehbPAAymj7CN/52P+lAhzRBBAIdnlnNvDEYFpyXT1ZM3Vy8TsEZNnIz7dIiB23KAv2b o8cg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=a6esfILiVwAsgJ/n0DJnTzrF+tCHTL0TuenWIqFN+S0=; b=X2WjZ2S6biE+njyrQOaGebNSb23YfNQFJ0OMP8pWk9zfyjtn3n+iOSsdIWQEE6fHCj edvA6ZtmqIJJeYXngl8KUy5ofPjw4eJivlyBn1jnjGJzghUkPcKXve7t94eMwftMp+a5 3B4fHm6zCTxutVmaiUqKGQCuSlmowthZKpuNlKiHe4bFYADCU7qkRH6pEEHCN6up0OSX 67mRPrWYHGFFaxsUH2hqh2sz/zirvM9CxLJezICo3AwrB9WLwDFMgg0iU1o4ANLg1x73 CdgELyxMfvLcAor2/X+5D5bS6jA+GHpbnmxQx0BDy5qZ4IVkQWEV1OYbRAwm1J8SNnpu +irw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=DXEiDgBR; 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 u23si4014139pfh.70.2022.01.21.11.04.24; Fri, 21 Jan 2022 11:04:36 -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=DXEiDgBR; 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 S1352089AbiASJei (ORCPT + 99 others); Wed, 19 Jan 2022 04:34:38 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:21116 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239651AbiASJeC (ORCPT ); Wed, 19 Jan 2022 04:34:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642584841; 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: in-reply-to:in-reply-to:references:references; bh=a6esfILiVwAsgJ/n0DJnTzrF+tCHTL0TuenWIqFN+S0=; b=DXEiDgBRLSaFIsCg5XClnG4jmLxFUWsoXXCVOYRgBIrOBic12ymVUdgjt/kkwuuIG3Ghf2 N2/5RERYRBr3NXCrUe4xznlR6cgjg/uQZ71jjv17C50pWiT4aO9y2dKQILGYImr3h9dCUp iCUz3SYpVsdgAK15DjY14LewHpM97M8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-551-rwAGmq2lOh6xY0z06WQcXA-1; Wed, 19 Jan 2022 04:33:58 -0500 X-MC-Unique: rwAGmq2lOh6xY0z06WQcXA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E64291091DA0; Wed, 19 Jan 2022 09:33:54 +0000 (UTC) Received: from localhost (ovpn-12-206.pek2.redhat.com [10.72.12.206]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6B7306A901; Wed, 19 Jan 2022 09:33:25 +0000 (UTC) Date: Wed, 19 Jan 2022 17:33:22 +0800 From: Baoquan He To: Alexandre Ghiti Cc: Jisheng Zhang , Russell King , Catalin Marinas , Will Deacon , Paul Walmsley , Palmer Dabbelt , Albert Ou , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, hpa@zytor.com, Eric Biederman , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, kexec@lists.infradead.org, Alexandre ghiti Subject: Re: [PATCH v2 0/5] kexec: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef Message-ID: <20220119093322.GC4977@MiWiFi-R3L-srv> References: <20211206160514.2000-1-jszhang@kernel.org> <20220116133847.GE2388@MiWiFi-R3L-srv> <20220119080859.GB4977@MiWiFi-R3L-srv> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/19/22 at 09:52am, Alexandre Ghiti wrote: > Hi Baoquan, > > On Wed, Jan 19, 2022 at 9:11 AM Baoquan He wrote: > > > > On 01/18/22 at 10:13pm, Jisheng Zhang wrote: > > > On Sun, Jan 16, 2022 at 09:38:47PM +0800, Baoquan He wrote: > > > > Hi Jisheng, > > > > > > Hi Baoquan, > > > > > > > > > > > On 12/07/21 at 12:05am, Jisheng Zhang wrote: > > > > > Replace the conditional compilation using "#ifdef CONFIG_KEXEC_CORE" > > > > > by a check for "IS_ENABLED(CONFIG_KEXEC_CORE)", to simplify the code > > > > > and increase compile coverage. > > > > > > > > I go through this patchset, You mention the benefits it brings are > > > > 1) simplity the code; > > > > 2) increase compile coverage; > > > > > > > > For benefit 1), it mainly removes the dummy function in x86, arm and > > > > arm64, right? > > > > > > Another benefit: remove those #ifdef #else #endif usage. Recently, I > > > fixed a bug due to lots of "#ifdefs": > > > http://lists.infradead.org/pipermail/linux-riscv/2021-December/010607.html > > > > Glad to know the fix. While, sometime the ifdeffery is necessary. I am > > sorry about the one in riscv and you have fixed, it's truly a bug . But, > > the increasing compile coverage at below you tried to make, it may cause > > issue. Please see below my comment. > > > > > > > > > > > > > For benefit 2), increasing compile coverage, could you tell more how it > > > > achieves and why it matters? What if people disables CONFIG_KEXEC_CORE in > > > > purpose? Please forgive my poor compiling knowledge. > > > > > > Just my humble opinion, let's compare the code:: > > > > > > #ifdef CONFIG_KEXEC_CORE > > > > > > code block A; > > > > > > #endif > > > > > > If KEXEC_CORE is disabled, code block A won't be compiled at all, the > > > preprocessor will remove code block A; > > > > > > If we convert the code to: > > > > > > if (IS_ENABLED(CONFIG_KEXEC_CORE)) { > > > code block A; > > > } > > > > > > Even if KEXEC_CORE is disabled, code block A is still compiled. > > > > This is what I am worried about. Before, if CONFIG_KEXEC_CORE is > > unset, those relevant codes are not compiled in. I can't see what > > benefit is brought in if compiled in the unneeded code block. Do I miss > > anything? > > > > This is explained in Documentation/process/coding-style.rst "21) > Conditional Compilation". Thanks for the pointer, Alex. I read that part, while my confusion isn't gone. With the current code, CONFIG_KEXEC_CORE is set, - reserve_crashkernel_low() and reserve_crashkernel() compiled in. CONFIG_KEXEC_CORE is unset, - reserve_crashkernel_low() and reserve_crashkernel() compiled out. After this patch applied, does it have the same effect as the old code? arch/x86/kernel/setup.c: before ====== #ifdef CONFIG_KEXEC_CORE static int __init reserve_crashkernel_low(void) { ...... } static void __init reserve_crashkernel(void) { ...... } #else static void __init reserve_crashkernel(void) { } #endif after ======= static int __init reserve_crashkernel_low(void) { ...... } static void __init reserve_crashkernel(void) { ...... if (!IS_ENABLED(CONFIG_KEXEC_CORE)) return; ...... }