From: Vlastimil Babka <vbabka@suse.cz>
To: Leonardo Bras <leobras@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jakub Kicinski <kuba@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] local_lock: Minor improvements of local_trylock*() documentation
Date: Wed, 28 May 2025 11:04:43 +0200 [thread overview]
Message-ID: <7faca175-64c2-4a12-9340-37eaeeb8bd3e@suse.cz> (raw)
In-Reply-To: <20250521174726.578303-1-leobras@redhat.com>
On 5/21/25 19:47, Leonardo Bras wrote:
> Fix local_trylock_init() documentation, as it was mentioning the non-try
> helper instead, and use the opportunity to make clear the try_lock*() needs
> to receive a local_trylock_t variable as parameter.
>
> Signed-off-by: Leonardo Bras <leobras@redhat.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
Locking tree (btw the local_lock files are missing in the list of
MAINTAINERS) or mm since this fixes up changes that went through mm recently?
> ---
> v1: https://lore.kernel.org/all/20250505170244.253170-1-leobras@redhat.com/
> RFC: https://lore.kernel.org/all/20250430073610.163846-1-leobras@redhat.com/
>
>
> include/linux/local_lock.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/local_lock.h b/include/linux/local_lock.h
> index 16a2ee4f8310b..d8d5e6cfa1151 100644
> --- a/include/linux/local_lock.h
> +++ b/include/linux/local_lock.h
> @@ -45,38 +45,38 @@
> /**
> * local_unlock_irqrestore - Release a per CPU local lock and restore
> * interrupt flags
> * @lock: The lock variable
> * @flags: Interrupt flags to restore
> */
> #define local_unlock_irqrestore(lock, flags) \
> __local_unlock_irqrestore(lock, flags)
>
> /**
> - * local_lock_init - Runtime initialize a lock instance
> + * local_trylock_init - Runtime initialize a local_trylock_t instance
> */
> #define local_trylock_init(lock) __local_trylock_init(lock)
>
> /**
> * local_trylock - Try to acquire a per CPU local lock
> - * @lock: The lock variable
> + * @lock: The local_trylock_t variable
> *
> * The function can be used in any context such as NMI or HARDIRQ. Due to
> * locking constrains it will _always_ fail to acquire the lock in NMI or
> * HARDIRQ context on PREEMPT_RT.
> */
> #define local_trylock(lock) __local_trylock(lock)
>
> /**
> * local_trylock_irqsave - Try to acquire a per CPU local lock, save and disable
> * interrupts if acquired
> - * @lock: The lock variable
> + * @lock: The local_trylock_t variable
> * @flags: Storage for interrupt flags
> *
> * The function can be used in any context such as NMI or HARDIRQ. Due to
> * locking constrains it will _always_ fail to acquire the lock in NMI or
> * HARDIRQ context on PREEMPT_RT.
> */
> #define local_trylock_irqsave(lock, flags) \
> __local_trylock_irqsave(lock, flags)
>
> DEFINE_GUARD(local_lock, local_lock_t __percpu*,
prev parent reply other threads:[~2025-05-28 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 17:47 Leonardo Bras
2025-05-28 9:04 ` Vlastimil Babka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7faca175-64c2-4a12-9340-37eaeeb8bd3e@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=kuba@kernel.org \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®