From: Peter Zijlstra <peterz@infradead.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] sched, x86: Update the comment for TIF_NEED_RESCHED_LAZY.
Date: Wed, 6 Nov 2024 18:20:44 +0100 [thread overview]
Message-ID: <20241106172044.GO10375@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241106162449.sk6rDddk@linutronix.de>
On Wed, Nov 06, 2024 at 05:24:49PM +0100, Sebastian Andrzej Siewior wrote:
> Add the "Lazy" part to the comment for TIF_NEED_RESCHED_LAZY so it is
> not the same as TIF_NEED_RESCHED.
But it is lazy to copy/paste and not bother with comments, right? :-)
Thanks!
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> arch/x86/include/asm/thread_info.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/include/asm/thread_info.h b/arch/x86/include/asm/thread_info.h
> index 75bb390f7baf5..a55c214f3ba64 100644
> --- a/arch/x86/include/asm/thread_info.h
> +++ b/arch/x86/include/asm/thread_info.h
> @@ -87,7 +87,7 @@ struct thread_info {
> #define TIF_NOTIFY_RESUME 1 /* callback before returning to user */
> #define TIF_SIGPENDING 2 /* signal pending */
> #define TIF_NEED_RESCHED 3 /* rescheduling necessary */
> -#define TIF_NEED_RESCHED_LAZY 4 /* rescheduling necessary */
> +#define TIF_NEED_RESCHED_LAZY 4 /* Lazy rescheduling needed */
> #define TIF_SINGLESTEP 5 /* reenable singlestep on user return*/
> #define TIF_SSBD 6 /* Speculative store bypass disable */
> #define TIF_SPEC_IB 9 /* Indirect branch speculation mitigation */
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-11-06 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 16:24 Sebastian Andrzej Siewior
2024-11-06 17:20 ` Peter Zijlstra [this message]
2024-11-11 10:58 ` [tip: sched/core] " tip-bot2 for Sebastian Andrzej Siewior
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=20241106172044.GO10375@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/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®