Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp2534637pxb; Sun, 16 Jan 2022 23:57:14 -0800 (PST) X-Google-Smtp-Source: ABdhPJwyvzQSYFwiwm2NhJfDViUxQ/rEsMqOONNaEElMCDas2fO+JdKpVrkT+4CkVBQzYB4304hQ X-Received: by 2002:a17:90a:b798:: with SMTP id m24mr32691038pjr.143.1642406234712; Sun, 16 Jan 2022 23:57:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642406234; cv=none; d=google.com; s=arc-20160816; b=A/3OtgC7RvVHfXsq3Wr7SeqkHQJC+UN6AJzllncC/plJ2N7Uakvch/Fv6mpskMmULE 8aQ+I6EMs8yLQqao7I/16J9LcCqpZx4Qj+PFu4/G44QHQfLGiLs1esD5gvNkBhPxb6aw OyYnKV4786YgzQKacfyYfbtKSTmNKpd+JmrqimjmTy0YAU3+tczviFj26oQpNI2sWVAd z0hdzHWOycEITX4CbrLPAQUIdp7oFn9Cxbv8zxMkYlBC3eekuEMtW+qGdHX+sG44+r0d jSAqo8p+zwyr7GOk5vCsGzjQfyWCgPRkHfLmzH1WOURvKgUVJ2s9jgtakKf8wMJbDqub SZeA== 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=cp5M2AGP5P4N6b6EQKr0vl4nAKthbkR6iiQTidIywuQ=; b=m3DaMlf0w8pz9LLoNFNeDqS2vsXCv6CGyMbrKRs83m2C+f9zLF/QXN/I+NjYzwpPqZ 3yPfh0GLB5TfLdPHV2i+33WHaUJkl3VYVJv+NvEKlpZju8tipOEPrWyadelsSKauSdvd wGdpypAZJVDeo+2G69Vuy785gRnhwhFGIPxzjTK3Ef1pSVwninfnuWVHKCvxOwGFuD+Z 2lNB/BQtzzaiTKDg6ZQInVfbzkY5wZ3xYz7Zaptwy2rKbKfrn+H967H4hUpI+Z+73b62 B46OUWk846/IWlXpx0jWlBbCjU0ysGPKdRFB63GTFuXGvTlLcdkwV23GA5pY+5nETWuT XfEw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=b4gYr5tr; 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 y12si13233430pgh.860.2022.01.16.23.56.39; Sun, 16 Jan 2022 23:57:14 -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=b4gYr5tr; 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 S235338AbiAPNjI (ORCPT + 99 others); Sun, 16 Jan 2022 08:39:08 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:33431 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233233AbiAPNjG (ORCPT ); Sun, 16 Jan 2022 08:39:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642340345; 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=cp5M2AGP5P4N6b6EQKr0vl4nAKthbkR6iiQTidIywuQ=; b=b4gYr5tri//+j84Dfnb1zxHYzoXTBJfC4F2+kxPJu+I2sBmhTfvXynQw+AtFxyad2EfC0j xxYplHqIhLV31NJnH4YETbRgl2Cci0uiEytA5jsn+zQY4iK6O8AS74/us5eyLDngMdUfzH lp346KClC2idleWzHWgRgY+nePq9Kmc= 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-663-xbtBAwTnOzqAyXi4zY5DnA-1; Sun, 16 Jan 2022 08:39:00 -0500 X-MC-Unique: xbtBAwTnOzqAyXi4zY5DnA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 2AF89802924; Sun, 16 Jan 2022 13:38:57 +0000 (UTC) Received: from localhost (ovpn-12-76.pek2.redhat.com [10.72.12.76]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9B9F7105C891; Sun, 16 Jan 2022 13:38:51 +0000 (UTC) Date: Sun, 16 Jan 2022 21:38:47 +0800 From: Baoquan He To: Jisheng Zhang Cc: 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: <20220116133847.GE2388@MiWiFi-R3L-srv> References: <20211206160514.2000-1-jszhang@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211206160514.2000-1-jszhang@kernel.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jisheng, 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? 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. Thanks Baoquan