Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 34B54C636D4 for ; Mon, 13 Feb 2023 20:43:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230292AbjBMUn0 (ORCPT ); Mon, 13 Feb 2023 15:43:26 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39584 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229762AbjBMUnW (ORCPT ); Mon, 13 Feb 2023 15:43:22 -0500 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 568BF11678; Mon, 13 Feb 2023 12:43:19 -0800 (PST) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1676320994; 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=Dp1zvkaoXZwXPfB60lKlFJ79KNQWFIG6r/rAvzVX2j0=; b=ATrfQerDAcuySUZMGbGGPfRvpO7npAochf0y/gEFwyOLTIIOPsj8F5UdAkSxAuzSynghnf IOTO5EIYTFw2xf6RGjBfpTmauEVcwJiCqQTA8T05F3f6G6s+EevdtwTTdJBsWR1QssCmgg aM+QcYbSdIBPGV/kNmC4Aqdeo/qW9Jr4Ont3IYOzB5kclf8eCe7Aemz4r0sbYiNy+1ef3F GnxAWxol9HnUs1qrXHAsf+4gVMHvgXlV/nxH082t6orE4Tsf+elk0lhY4ikDJqDwdo5CnK HrQtSy+hD7BEAD4hExx+eXs4e9INIQhxzIky2MxurVGaDq8YEnf9jIsB+9bjiw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1676320994; 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=Dp1zvkaoXZwXPfB60lKlFJ79KNQWFIG6r/rAvzVX2j0=; b=6eDvXLZWiDP8EzoHgPZhWlwqyjjkAVVINrVfhH+zO1xQGi/EoSnQT2gRD64pSmE2WioiC2 v5mGOkovIxH/GsAg== To: Usama Arif , dwmw2@infradead.org, kim.phillips@amd.com Cc: arjan@linux.intel.com, mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com, x86@kernel.org, pbonzini@redhat.com, paulmck@kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, rcu@vger.kernel.org, mimoja@mimoja.de, hewenliang4@huawei.com, thomas.lendacky@amd.com, seanjc@google.com, pmenzel@molgen.mpg.de, fam.zheng@bytedance.com, punit.agrawal@bytedance.com, simon.evans@bytedance.com, liangma@liangbit.com, David Woodhouse , Usama Arif Subject: Re: [PATCH v8 9/9] x86/smpboot: Serialize topology updates for secondary bringup In-Reply-To: <20230209154156.266385-10-usama.arif@bytedance.com> References: <20230209154156.266385-1-usama.arif@bytedance.com> <20230209154156.266385-10-usama.arif@bytedance.com> Date: Mon, 13 Feb 2023 21:43:13 +0100 Message-ID: <87v8k5s3dq.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 09 2023 at 15:41, Usama Arif wrote: > From: David Woodhouse > > The toplogy update is performed by the AP via smp_callin() after the BSP > has called do_wait_cpu_initialized(), setting the AP's bit in > cpu_callout_mask to allow it to proceed. > > In preparation to enable further parallelism of AP bringup, add locking to > serialize the update even if multiple APs are (in future) permitted to > proceed through the next stages of bringup in parallel. This one is also only relevant for further parallelisation, right? Thanks, tglx