Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp6228061pxb; Thu, 27 Jan 2022 09:05:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJxQS2JNgY0XLURYc/lZdw11aJ2oT3vCLnpibBAeYIcQ+K2KMSxcNNdXJ4VcWFCQqifft5AK X-Received: by 2002:a17:90b:4ad1:: with SMTP id mh17mr5041402pjb.135.1643303135406; Thu, 27 Jan 2022 09:05:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643303135; cv=none; d=google.com; s=arc-20160816; b=AeRo5m+XLi9BoruscPikIDLoJ2YrCkBxC9TWyuEJz5WuMhgBDlwLciL3BRdKDY2AWr SbcVgvf6bgn+A4W0TLUUU4j4H9fnLgH917XJNOTLdKyzo6WrswM89un3UwwkzboWouAf AfPY0zMLppf0cPCT8EcZRtEe/xXQ5I9aXpkENhpawWkGbqCXFUAWGDPuOrj1LBRAyx7e 1CFSkw46SsxlbxCiVC2s6apMm8AREWx1PtqAnRji/K25wnryCwLLSlegEjO+8rQf5uKB BPik3tQe8d7kvA8qkad6NJGjhsk5JIVw4HsXMMM/Z6tei1UITKv8XnQzvL1KF8nkgWJU nUQA== 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=ZyJ4J5e+3GKlvkcYQ+urtekvThyzHXZ6mJY5flPNI2w=; b=msPJM1CThyn17M/bhB6nQJ6WSoR3wOSqAH8Jtbm2k3lzm6hUyr+ib985k9LLRYqmo4 KOBH6eEymnAzy7O9mR9U/X4/4nQu/Gi/iEL4JKzCUpV/gb3lhBSaghU6GBBfqM0nxBS4 N7LgZ/A+n+I1H5gvexAhpVIMYXhSsBJQC4//D5nnvCDTVxNGkKSqz6wCS7l9IYn1vA7K Ugn9PLEBgemICvOeKJNkVU4C2viOHB1fhb+DUtnb3PpOKRJknc12M125oRFC38rlyCnA ZIAF9EGZwqM7SeWOmgQawhqOwP3Pct3Re3ZsVF6pMq3W7cCk9IX7r7B1YV2kCLsZHy8U v9yA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Vd5sZ3dC; 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 j66si2442171pgc.858.2022.01.27.09.04.23; Thu, 27 Jan 2022 09:05:35 -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=Vd5sZ3dC; 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 S238729AbiA0Jl7 (ORCPT + 99 others); Thu, 27 Jan 2022 04:41:59 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:52770 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238725AbiA0Jl5 (ORCPT ); Thu, 27 Jan 2022 04:41:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643276516; 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=ZyJ4J5e+3GKlvkcYQ+urtekvThyzHXZ6mJY5flPNI2w=; b=Vd5sZ3dC7/pYBaGh+bF1xyrJq48A3qZZlBSQRvNx7JgVIy6XXx1EfCzkBHtcRJzjMMAoUJ t1pyPjjVGGQ3/mFoAMnjD53hTW+xESWPYOEuqMI2aID0CUU/Hah4ZuxVD2WA9FzCMpWtyl 8JqBRJWi3B7QsASuT6NuSDR4uHHHZBs= 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-401-Z12YeTdsM2i_9Q-z2YbW8A-1; Thu, 27 Jan 2022 04:41:50 -0500 X-MC-Unique: Z12YeTdsM2i_9Q-z2YbW8A-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 78C56814514; Thu, 27 Jan 2022 09:41:48 +0000 (UTC) Received: from localhost (ovpn-13-51.pek2.redhat.com [10.72.13.51]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7B911105915D; Thu, 27 Jan 2022 09:41:47 +0000 (UTC) Date: Thu, 27 Jan 2022 17:41:44 +0800 From: Baoquan He To: Pingfan Liu Cc: linux-kernel@vger.kernel.org, Eric Biederman , Peter Zijlstra , Thomas Gleixner , Valentin Schneider , Vincent Donnefort , Ingo Molnar , Mark Rutland , YueHaibing , Baokun Li , Randy Dunlap , kexec@lists.infradead.org Subject: Re: [PATCHv2] kexec: disable cpu hotplug until the rebooting cpu is stable Message-ID: <20220127094144.GC13508@MiWiFi-R3L-srv> References: <20220127090215.32000-1-kernelfans@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220127090215.32000-1-kernelfans@gmail.com> 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 Pingfan, On 01/27/22 at 05:02pm, Pingfan Liu wrote: > The following identical code piece appears in both > migrate_to_reboot_cpu() and smp_shutdown_nonboot_cpus(): > > if (!cpu_online(primary_cpu)) > primary_cpu = cpumask_first(cpu_online_mask); > > This is due to a breakage like the following: > migrate_to_reboot_cpu(); > cpu_hotplug_enable(); > --> comes a cpu_down(this_cpu) on other cpu > machine_shutdown(); > > Although the kexec-reboot task can get through a cpu_down() on its cpu, > this code looks a little confusing. > > Make things straight forward by keeping cpu hotplug disabled until > smp_shutdown_nonboot_cpus() holds cpu_add_remove_lock. By this way, the > breakage is squashed out and the rebooting cpu can keep unchanged. If I didn't go through code wrongly, you may miss the x86 case. Several ARCHes do call smp_shutdown_nonboot_cpus() in machine_shutdown() in kexec reboot code path, while x86 doesn't. If I am right, you may need reconsider if this patch is needed or need be adjustd. Are you optimizing code path, or you meet a real problem? I haven't checked v1, but I also didn't see it's told in patch log which case it is. > > Note: this patch only affects the kexec-reboot on arches, which rely on > cpu hotplug mechanism. > > Signed-off-by: Pingfan Liu > Cc: Eric Biederman > Cc: Peter Zijlstra > Cc: Thomas Gleixner > Cc: Valentin Schneider > Cc: Vincent Donnefort > Cc: Ingo Molnar > Cc: Mark Rutland > Cc: YueHaibing > Cc: Baokun Li > Cc: Randy Dunlap > Cc: Valentin Schneider > Cc: kexec@lists.infradead.org > To: linux-kernel@vger.kernel.org > --- > v1 -> v2: > improve commit log > > kernel/cpu.c | 16 ++++++++++------ > kernel/kexec_core.c | 10 ++++------ > 2 files changed, 14 insertions(+), 12 deletions(-) > > diff --git a/kernel/cpu.c b/kernel/cpu.c > index 9c92147f0812..87bdf21de950 100644 > --- a/kernel/cpu.c > +++ b/kernel/cpu.c > @@ -1240,20 +1240,24 @@ int remove_cpu(unsigned int cpu) > } > EXPORT_SYMBOL_GPL(remove_cpu); > > +/* primary_cpu keeps unchanged after migrate_to_reboot_cpu() */ > void smp_shutdown_nonboot_cpus(unsigned int primary_cpu) > { > unsigned int cpu; > int error; > > + /* > + * Block other cpu hotplug event, so primary_cpu is always online if > + * it is not touched by us > + */ > cpu_maps_update_begin(); > - > /* > - * Make certain the cpu I'm about to reboot on is online. > - * > - * This is inline to what migrate_to_reboot_cpu() already do. > + * migrate_to_reboot_cpu() disables CPU hotplug assuming that > + * no further code needs to use CPU hotplug (which is true in > + * the reboot case). However, the kexec path depends on using > + * CPU hotplug again; so re-enable it here. > */ > - if (!cpu_online(primary_cpu)) > - primary_cpu = cpumask_first(cpu_online_mask); > + __cpu_hotplug_enable(); > > for_each_online_cpu(cpu) { > if (cpu == primary_cpu) > diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c > index 68480f731192..db4fa6b174e3 100644 > --- a/kernel/kexec_core.c > +++ b/kernel/kexec_core.c > @@ -1168,14 +1168,12 @@ int kernel_kexec(void) > kexec_in_progress = true; > kernel_restart_prepare("kexec reboot"); > migrate_to_reboot_cpu(); > - > /* > - * migrate_to_reboot_cpu() disables CPU hotplug assuming that > - * no further code needs to use CPU hotplug (which is true in > - * the reboot case). However, the kexec path depends on using > - * CPU hotplug again; so re-enable it here. > + * migrate_to_reboot_cpu() disables CPU hotplug. If an arch > + * relies on the cpu teardown to achieve reboot, it needs to > + * re-enable CPU hotplug there. > */ > - cpu_hotplug_enable(); > + > pr_notice("Starting new kernel\n"); > machine_shutdown(); > } > -- > 2.31.1 >