[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4c0a8190-bd9f-4886-a156-854ae831b16a@redhat.com>
Date: Fri, 5 Apr 2024 11:32:56 +0200
From: Daniel Bristot de Oliveira <bristot@...hat.com>
To: "Joel Fernandes (Google)" <joel@...lfernandes.org>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>, Peter Zijlstra <peterz@...radead.org>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
Jonathan Corbet <corbet@....net>
Cc: Suleiman Souhlal <suleiman@...gle.com>,
Youssef Esmat <youssefesmat@...gle.com>, Steven Rostedt
<rostedt@...dmis.org>, David Vernet <void@...ifault.com>,
"Paul E . McKenney" <paulmck@...nel.org>, joseph.salisbury@...onical.com,
Dietmar Eggemann <dietmar.eggemann@....com>, Ben Segall
<bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Valentin Schneider <vschneid@...hat.com>,
Luca Abeni <luca.abeni@...tannapisa.it>,
Tommaso Cucinotta <tommaso.cucinotta@...tannapisa.it>,
Vineeth Pillai <vineeth@...byteword.org>,
Shuah Khan <skhan@...uxfoundation.org>, Phil Auld <pauld@...hat.com>,
linux-doc@...r.kernel.org
Subject: Re: [PATCH v2 09/15] admin-guide/hw-vuln: Correct prctl() argument
description
On 3/13/24 02:24, Joel Fernandes (Google) wrote:
> Correct the description for arg4 which appears to be outdated.
>
> Signed-off-by: Joel Fernandes (Google) <joel@...lfernandes.org>
Maybe it is better to keep these tests into a separated thread (?) Because they
are touching things that are not about the server, so it might create conflicts...
What I did in the past when adding a series that was part in the kernel (tracer)
and part of tools (rtla) was to split them into two series, then referencing
one on the other - Steven suggested... and it was a good thing... and
reduced the number of versions.
So I am not adding these self-tests on top of the dl series for now... because
there is also discussion about the patches... and I am not an expert in the
selftests.... I will add a reference to this thread in the v6 cover and keep
updating it as new versions show up... in this way, one thing does not block
the other.
Thoughts?
-- Daniel
> ---
> Documentation/admin-guide/hw-vuln/core-scheduling.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/hw-vuln/core-scheduling.rst b/Documentation/admin-guide/hw-vuln/core-scheduling.rst
> index cf1eeefdfc32..338d639a8127 100644
> --- a/Documentation/admin-guide/hw-vuln/core-scheduling.rst
> +++ b/Documentation/admin-guide/hw-vuln/core-scheduling.rst
> @@ -62,8 +62,8 @@ arg3:
>
> arg4:
> ``pid_type`` for which the operation applies. It is one of
> - ``PR_SCHED_CORE_SCOPE_``-prefixed macro constants. For example, if arg4
> - is ``PR_SCHED_CORE_SCOPE_THREAD_GROUP``, then the operation of this command
> + ``PIDTIME_``-prefixed macro constants. For example, if arg4
> + is ``PIDTYPE_TGID``, then the operation of this command
> will be performed for all tasks in the task group of ``pid``.
>
> arg5:
Powered by blists - more mailing lists