From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zytor.com (terminus.zytor.com [198.137.202.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AD60239B958 for ; Mon, 30 Mar 2026 19:44:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.136 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774899844; cv=none; b=gYY1ZNWGSNMzcelh+WNE9gAoFASIJKl1kTBJ1SXc0GUcDT1w/hUnNsh7jdV9syWxYVtMkt0RrCfrBrdIrkVItEh2k7Ws07BjV1rG8+rutUm9PxupqKITI0BjZvvTu6xcRMSVmuy6jXiGMYWY7wgCSLmzpyKguRKKmde1km1d57g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774899844; c=relaxed/simple; bh=UaqceGCwuhC16ewV2zMqqVdhoV8GMRAONq64AjGDuAk=; h=Date:From:To:CC:Subject:In-Reply-To:References:Message-ID: MIME-Version:Content-Type; b=ooHmI4t7blb5yTQjJVEPOlm5FBXz5VOa26e8BedXs6xYPoj7gDd/0qGK2PtiBiIeRu3Jzlb803mIJt8RNJFpbIgimrdyKe/4pXw730/BW8NkoSiOuWWozZWvk6HF3y594RdC9k7BwwsQoSTI7/M3pcekxPq8Qb2Wu/hA37CM1Os= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com; spf=pass smtp.mailfrom=zytor.com; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b=iskndIEs; arc=none smtp.client-ip=198.137.202.136 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zytor.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b="iskndIEs" Received: from ehlo.thunderbird.net (c-76-133-66-138.hsd1.ca.comcast.net [76.133.66.138]) (authenticated bits=0) by mail.zytor.com (8.18.1/8.17.1) with ESMTPSA id 62UJh9Gg2472398 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 30 Mar 2026 12:43:09 -0700 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 62UJh9Gg2472398 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2026032601; t=1774899790; bh=UaqceGCwuhC16ewV2zMqqVdhoV8GMRAONq64AjGDuAk=; h=Date:From:To:CC:Subject:In-Reply-To:References:From; b=iskndIEsn8qg9B6u52xsVGJBbchtq3fTJ79nuAZAnHTVOxPlsc4wBsv6K44mQNy/w 7/nUhspLyKEbrNBthkxQdzwGRt1nZm2pZ+TZGYEbUVyMvwJfgU7Fan9gO2Ykt9/oaA gTM0fR/Z3BM/dHD/nPdvvKMTHJjJFw36nW79GS69zjLFhlqu4OJ/Wc9S7ur6b/JHDs AO66Gb1KChEIf1kUaEkpeXthvSKDNZgjpOIGFRE7P3vHSBbeCWHu4Ij+VcAMdwk6A8 oOJ48L9YdE4LKSMa3LHj5mGAHOGv7ug5E1/dAIXa7N0yJQSpObtPOpfTAN70tJNbeB V5k3Gzh5UBsjQ== Date: Mon, 30 Mar 2026 12:43:04 -0700 From: "H. Peter Anvin" To: Peter Zijlstra , Borislav Petkov CC: Mike Rapoport , x86@kernel.org, Bert Karwatzki , Dave Hansen , Ingo Molnar , Thomas Gleixner , linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86/alternative: delay freeing of smp_locks section User-Agent: K-9 Mail for Android In-Reply-To: <20260330193625.GF3558198@noisy.programming.kicks-ass.net> References: <20260328081634.797552-1-rppt@kernel.org> <20260328114118.GAace-Xu8bEKacpCtZ@fat_crate.local> <20260328195827.GCacgy44vl3_AUvhVr@fat_crate.local> <20260330174400.GEacq2YHnyomxVzXwp@fat_crate.local> <20260330193625.GF3558198@noisy.programming.kicks-ass.net> Message-ID: <306B9D7C-C6D0-43C6-9BDD-2FDF5DD5D2C3@zytor.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On March 30, 2026 12:36:25 PM PDT, Peter Zijlstra = wrote: >On Mon, Mar 30, 2026 at 07:44:00PM +0200, Borislav Petkov wrote: >> On Mon, Mar 30, 2026 at 08:16:32PM +0300, Mike Rapoport wrote: >> > Since this fixes a fallout from memblock changes, I can take it toget= her >> > with them via memblock tree with Ack from x86 folks if you prefer=2E >>=20 >> Sure, once you send me a patch with a proper explanation which I can ac= k=2E=2E=2E :) > >Another silly question; why not delete the whole SMP locks thing? I >mean, who cares about UP these days? Specifically, who cares about *running SMP kernels on UP?* Compiling for UP explicitly is an entirely different matter=2E