All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Gopi Krishna Menon <krishnagopi487@gmail.com>,
	Ivan Pravdin <ipravdin.official@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Tomas Glozar <tglozar@redhat.com>
Subject: Re: linux-next: manual merge of the ftrace tree with the jc_docs tree
Date: Fri, 21 Nov 2025 10:07:43 +0700	[thread overview]
Message-ID: <aR_Xf1qyNMnxXebl@archie.me> (raw)
In-Reply-To: <20251121123509.5f07d818@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

On Fri, Nov 21, 2025 at 12:35:09PM +1100, Stephen Rothwell wrote:
> diff --cc Documentation/tools/rtla/common_options.txt
> index 1c4f3e663cf5,edc8e850f5d0..000000000000
> --- a/Documentation/tools/rtla/common_options.txt
> +++ b/Documentation/tools/rtla/common_options.txt
> @@@ -46,9 -42,7 +46,9 @@@
>           - *f:prio* - use SCHED_FIFO with *prio*;
>           - *d:runtime[us|ms|s]:period[us|ms|s]* - use SCHED_DEADLINE with *runtime* and *period* in nanoseconds.
>   
>  +        If not set, tracer threads keep their default priority. For rtla user threads, it is set to SCHED_FIFO with priority 95. For kernel threads, see *osnoise* and *timerlat* tracer documentation for the running kernel version.
>  +
> - **-C**, **--cgroup**\[*=cgroup*]
> + **-C**, **--cgroup** \[*cgroup*]
>   
>           Set a *cgroup* to the tracer's threads. If the **-C** option is passed without arguments, the tracer's thread will inherit **rtla**'s *cgroup*. Otherwise, the threads will be placed on the *cgroup* passed to the option.
>   

The resolution LGTM, thanks!

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-11-21  3:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  1:35 linux-next: manual merge of the ftrace tree with the jc_docs tree Stephen Rothwell
2025-11-21  3:07 ` Bagas Sanjaya [this message]
2025-11-26 10:07 ` Gopi Krishna Menon
  -- strict thread matches above, loose matches on Subject: below --
2023-02-15  1:16 Stephen Rothwell
2023-02-15  2:03 ` Bagas Sanjaya
2023-02-13  1:24 Stephen Rothwell
2021-08-20  4:02 Stephen Rothwell
2018-03-21  4:31 Stephen Rothwell
2018-03-21  4:37 ` Stephen Rothwell
2018-03-21 13:15   ` Steven Rostedt
2018-03-21 20:55     ` Tom Zanussi
2018-03-21 22:21       ` Stephen Rothwell
2018-03-21 23:09         ` Tom Zanussi
2018-03-22 13:41         ` Steven Rostedt

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=aR_Xf1qyNMnxXebl@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=ipravdin.official@gmail.com \
    --cc=krishnagopi487@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglozar@redhat.com \
    /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.