All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Costa Shulyupin <costa.shul@redhat.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] docs: sysctl: timer_migration is for hrtimer only
Date: Mon, 31 Aug 2026 15:46:02 -0600	[thread overview]
Message-ID: <87se3uezfp.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260826132921.294142-1-costa.shul@redhat.com>

Costa Shulyupin <costa.shul@redhat.com> writes:

> 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.

Applied, thanks.

jon

      parent reply	other threads:[~2026-08-31 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 13:29 [PATCH v1] docs: sysctl: timer_migration is for hrtimer only Costa Shulyupin
2026-08-26 17:04 ` Bradley Morgan
2026-08-31 21:46 ` Jonathan Corbet [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=87se3uezfp.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=costa.shul@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.