From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (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 C8A763D9DC2; Fri, 24 Apr 2026 19:44:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777059861; cv=none; b=mTpRpJ+aIaZqHNAJ+PZ3u7FjNNmAIWfF5PZg1Ffu3F6HI9MUJq6Jvc743iHOZsFnNL3WaTpTTaxns9qeUlWtLjbUKs2ZjMch6i0r5O6tg9+B4rQvHiKjIjnRSxEaJs74cjXhCKBp88FXfRLbO+hAv7Bh2j8eTIxOKR3dd7TxoEY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777059861; c=relaxed/simple; bh=Rv1h3iMVnDwYM9WG0Iqg1RxCc654GhyoQ7lLcU+Zr20=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=OGGEbaeAta/7M5S3GfxidI1cVGVEGbgbPwuBYTjyBghxVKeUjetIEphzTHCaLAtyLbGsNaqKSRPYuV3BQWNPco+i9p+UD9TM7iJjB4uK3we8SeSlbzhlCYUMotvEUoBFf0+xaNgPpqt67+hL0+j6SHc+/MwVPKfMLDSQCTnnWCI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=4RH1XcFR; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=iqLfAh0z; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="4RH1XcFR"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="iqLfAh0z" From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1777059857; 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=2+rliU4cCrurJTfrKWYSNMc97AT2PbQ8kt0LrYzMJys=; b=4RH1XcFRCUI4pUKFbbaE2ynLn8NOaT602kfQD31J3RDvJfJo7XD92FNpJWLLlcewr0T0mx vN065gMMtlaUbKpjo3gXmlXENzp23fTKmDuJxX9zay6l/eNhSStIrom9wHBQBfbpJhHUA1 n1WNq9N84pxe7o/+aHeImeRSB/w6hav2SbDOfsSgxSIfr/h2nypcGrNEJ6dmcmcKyN/V6z rijeVmFkNDQY6InHkE5L5GhmFG5i2y1E9RO2nJwnNqaelod8gOb4/N9/+AJiTaWHK5f013 w/eRZCDT3NHFxYWTwvBUMPhyE9BD8eLGG77wcpWUwsrikwt4aL2/Kd6ACssj7g== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1777059857; 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=2+rliU4cCrurJTfrKWYSNMc97AT2PbQ8kt0LrYzMJys=; b=iqLfAh0zDX4+KsEUDE175S10unwiIU8nPBL256ZhVyzK9+tvLFrNWGmxv0kvMxKW1j2tRu GSek67fxRGEDh5BQ== To: Peter Zijlstra Cc: Mathias Stearn , Dmitry Vyukov , Jinjie Ruan , linux-man@vger.kernel.org, Mark Rutland , Mathieu Desnoyers , Catalin Marinas , Will Deacon , Boqun Feng , "Paul E. McKenney" , Chris Kennelly , regressions@lists.linux.dev, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Ingo Molnar , Blake Oler Subject: Re: [REGRESSION] rseq: refactoring in v6.19 broke everyone on arm64 and tcmalloc everywhere In-Reply-To: <20260424150318.GE641209@noisy.programming.kicks-ass.net> References: <87wlxy22x7.ffs@tglx> <87ik9i0xlj.ffs@tglx> <87a4ut1njh.ffs@tglx> <87v7dgzbo7.ffs@tglx> <20260424150318.GE641209@noisy.programming.kicks-ass.net> Date: Fri, 24 Apr 2026 21:44:16 +0200 Message-ID: <87se8kywhb.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Fri, Apr 24 2026 at 17:03, Peter Zijlstra wrote: > On Fri, Apr 24, 2026 at 04:16:08PM +0200, Thomas Gleixner wrote: >> > I was really hoping that we would only need to do the "redundant" >> > cpu_id_start writes would only be needed on membarrier_rseq IPIs where >> > it really is a pay-for-what-you-use functionality, >> >> That's fine and can be solved without adding this sequence overhead into >> the scheduler hotpath. > > Something like so? (probably needs help for !GENERIC bits) Yes and yes :) Let me stare at that !generic tif bits case.