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 E5B731372 for ; Sat, 28 Jun 2025 08:08:05 +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=1751098088; cv=none; b=PrYhQBrpjdAGH5YO/Rb24G7lf5EfRVRbR7y5NLWLN4qZ72uy035WCnVbK091SGcwXslkS3duWI+TJYEDPoVqXrAO+SPXAp7Lzxrj8VvRHE2GTW7TBOkf5XcF8Hm2jnwQo4MeJ/nRgPA8KJ5TWNuGG2AqPj/G9psUyBDGHnEgz10= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751098088; c=relaxed/simple; bh=3UhXg0hgehcghVQpMtzWRIUY64Ax+APcPYx8IU8QTnM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=LOoY4Aftq+05Pezb/IVPTqCYf7Cf1wOoDBM7kgayGp4UDS0iBnCAduIkPgKHy36fcXuD60hYj+WPmryeNjg+JGlJkoa38bXw4yTim3zApKDTRL4juFHXmAhzOAP6BXczmLRhehLO5P+NtuEtUP3ha2GQTmzLG8Thxy0OTPF4SYw= 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=S5eijEON; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=AdyafLun; 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="S5eijEON"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="AdyafLun" Date: Sat, 28 Jun 2025 10:08:01 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1751098082; 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=HoeSQkIBv25z0Tbqv1MKQk4IGR8oe+jHuinax4DpWyQ=; b=S5eijEONnGlCuaVoiSYRx2iBQyhh9SgR6PdVtRSCI9YWN5+jg/XbhTYQ7ihZNx8oKPyqKg sKCnzMEebZDIAVjtAO9si3/dOZQUHqmlWLPTROVj9WW3uSawvkdTWcBgePQgkZ4QUr8GwG pVbGomz0GjDWEF9TwI1ZQBXxFDNmgPAwrTli9fqT8MPAcgesWLk1Tf1Ts1Rnq3RtuOFfFu URyW/M1PiZhOY/ymf/Lx/P1Wamy2oakQv04QJItuaT7v6XK/Qwk4e4MYahVIg073QLQQrX XtUaT8aEQagF7yFl7n+iXT4FMqkTiQzwi8bqroSW8i8kh15z8bkUTARU7MtSWw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1751098082; 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=HoeSQkIBv25z0Tbqv1MKQk4IGR8oe+jHuinax4DpWyQ=; b=AdyafLun3rD95IR2OrjZ34cvouFduVwt+3HuO6JKUfaO53X19279Ch6vACKkuCuloC4ekv CgqQmloQw1TMtxAw== From: Sebastian Andrzej Siewior To: linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev Cc: tglx@linutronix.de, Peter Zijlstra , Ingo Molnar , Will Deacon , Waiman Long , Boqun Feng , Alexei Starovoitov Subject: Re: [PATCH v2 1/1] local_lock: Move this_cpu_ptr() notation from internal to main header. Message-ID: <20250628080801.qZq1OGYR@linutronix.de> References: <20250610110205.1111719-1-bigeasy@linutronix.de> <20250610110205.1111719-2-bigeasy@linutronix.de> 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-Disposition: inline In-Reply-To: <20250610110205.1111719-2-bigeasy@linutronix.de> On 2025-06-10 13:02:04 [+0200], To linux-kernel@vger.kernel.org wrote: > The local_lock.h is the main entry for the local_lock_t type and > provides wrappers around internal functions prefixed with __ in > local_lock_internal.h. > > Move the this_cpu_ptr() dereference of the variable from the internal to > the main header. Since it is all macro implemented, this_cpu_ptr() will > still happen within the preempt/ IRQ disabled section. > This will free the internal implementation (__) to be used on > local_lock_t types which are local variables and must not be accessed > via this_cpu_ptr(). > > Signed-off-by: Sebastian Andrzej Siewior A gentle ping. Sebastian