From: Bradley Morgan <brads@mainlining.org>
To: costa.shul@redhat.com
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org,
skhan@linuxfoundation.org, joel.granados@kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH v1] docs: sysctl: timer_migration is for hrtimer only
Date: Wed, 26 Aug 2026 18:04:50 +0100 [thread overview]
Message-ID: <1A262560-9593-4F00-BF40-CE758DB46C61@mainlining.org> (raw)
In-Reply-To: <20260826132921.294142-1-costa.shul@redhat.com>
On 26 August 2026 14:29:19 BST, Costa Shulyupin <costa.shul@redhat.com>
wrote:
+ CC joel.granados@kernel.org (sysctl folk)
+CC akpm@linux-foundation.org
>Since commit b2cf7507e1864 ("timers: Always queue timers on the local
>CPU") __mod_timer() no longer depends on timers_migration_enabled. Only
>high-resolution timer migration from isolated to housekeeping CPUs
>depends on it.
>
>Update and clarify the documentation accordingly.
>
>Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
>---
> Documentation/admin-guide/sysctl/kernel.rst | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
>diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
>index b6328cd0f43e..fb38d654846d 100644
>--- a/Documentation/admin-guide/sysctl/kernel.rst
>+++ b/Documentation/admin-guide/sysctl/kernel.rst
>@@ -1609,8 +1609,10 @@ If a value outside of this range is written to ``threads-max`` an
> timer_migration
> ===============
>
>-When set to a non-zero value, attempt to migrate timers away from idle cpus to
>-allow them to remain in low power states longer.
>+When set to a non-zero value, attempt to migrate high-resolution timers from
>+nohz isolated (nohz_full) to housekeeping CPUs.
>+See Documentation/admin-guide/cpu-isolation.rst
>+and Documentation/admin-guide/kernel-parameters.rst.
>
Hmm, ok!
Reviewed-by: Bradley Morgan <brads@mainlining.org>
> Default is set (1).
>
>
--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/
next prev parent reply other threads:[~2026-08-26 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 13:29 Costa Shulyupin
2026-08-26 17:04 ` Bradley Morgan [this message]
2026-08-31 21:46 ` Jonathan Corbet
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=1A262560-9593-4F00-BF40-CE758DB46C61@mainlining.org \
--to=brads@mainlining.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=joel.granados@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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®