[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877c6x9vcy.fsf@trenco.lwn.net>
Date: Tue, 14 Jan 2025 10:08:13 -0700
From: Jonathan Corbet <corbet@....net>
To: Phil Auld <pauld@...hat.com>, linux-kernel@...r.kernel.org
Cc: linux-doc@...r.kernel.org
Subject: Re: [PATCH] Documentation/sysctl: Add timer_migration to kernel.rst
Phil Auld <pauld@...hat.com> writes:
> There is no mention of timer_migration in the docs. Add
> a short description.
>
> Signed-off-by: Phil Auld <pauld@...hat.com>
> Cc: Jonathan Corbet <corbet@....net>
> Cc: linux-doc@...r.kernel.org
> ---
> Documentation/admin-guide/sysctl/kernel.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index b2b36d0c3094..e03691e2cf4a 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -1544,6 +1544,13 @@ constant ``FUTEX_TID_MASK`` (0x3fffffff).
> If a value outside of this range is written to ``threads-max`` an
> ``EINVAL`` error occurs.
>
> +timer_migration
> +===============
> +
> +When set, attempt to migrate timers away from idle cpus to allow them to remain
> +in low power states longer.
> +
> +Default is set.
When set to *what*? It will always be set to *some* value, right? So
we should really say what the specific values mean.
Thanks,
jon
Powered by blists - more mailing lists