From: Tomas Glozar <tglozar@redhat.com>
To: furkanonder <furkanonder@protonmail.com>
Cc: "linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] tools/rtla: Code Cleanup and Readability Improvements for timerlat
Date: Mon, 21 Oct 2024 10:19:36 +0200 [thread overview]
Message-ID: <CAP4=nvR8CzLo1SdJJ67WjpMHGHzb35g1DRXeDPyENLmyvMLsQQ@mail.gmail.com> (raw)
In-Reply-To: <I89kxpG3ElxMtO0ctkqvwK_7e-aVqnL2_bprS5snA3hgizDIw-76cJI6Vm4luKoVGwdRtAoHcYnxuYrzEPsMeqipZTYao5fGFs3b1ZTCQRY=@protonmail.com>
ne 20. 10. 2024 v 22:01 odesílatel furkanonder
<furkanonder@protonmail.com> napsal:
>
> The enhancements made to timerlat_load.py are intended to improve the
> script's robustness and readability.
>
> Summary of the changes:
> - Unnecessary semicolons at the end of lines have been removed.
> - Parentheses surrounding the if statement checking args.prio have been
> eliminated.
> - String concatenation for constructing timerlat_path has been replaced
> with an f-string.
> - Spacing in a multiplication expression has been adjusted for improved
> clarity.
>
> Signed-off-by: Furkan Onder <furkanonder@protonmail.com>
> ---
> tools/tracing/rtla/sample/timerlat_load.py | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tools/tracing/rtla/sample/timerlat_load.py b/tools/tracing/rtla/sample/timerlat_load.py
> index 8cc5eb2d2e69..785e9a83539a 100644
> --- a/tools/tracing/rtla/sample/timerlat_load.py
> +++ b/tools/tracing/rtla/sample/timerlat_load.py
> @@ -37,12 +37,12 @@ except:
> exit(1)
>
> try:
> - os.sched_setaffinity(0, affinity_mask);
> + os.sched_setaffinity(0, affinity_mask)
> except:
> print("Error setting affinity")
> exit(1)
>
> -if (args.prio):
> +if args.prio:
> try:
> param = os.sched_param(int(args.prio))
> os.sched_setscheduler(0, os.SCHED_FIFO, param)
> @@ -51,21 +51,21 @@ if (args.prio):
> exit(1)
>
> try:
> - timerlat_path = "/sys/kernel/tracing/osnoise/per_cpu/cpu" + args.cpu + "/timerlat_fd"
> + timerlat_path = f"/sys/kernel/tracing/osnoise/per_cpu/cpu{args.cpu}/timerlat_fd"
> timerlat_fd = open(timerlat_path, 'r')
> except:
> print("Error opening timerlat fd, did you run timerlat -U?")
> exit(1)
>
> try:
> - data_fd = open("/dev/full", 'r');
> + data_fd = open("/dev/full", 'r')
> except:
> print("Error opening data fd")
>
> while True:
> try:
> timerlat_fd.read(1)
> - data_fd.read(20*1024*1024)
> + data_fd.read(20 * 1024 * 1024)
> except:
> print("Leaving")
> break
> --
> 2.46.2
>
The code part looks good now, thank you! Just one comment: the commit
titles should include more clearly which part of timerlat it is
changing: timerlat_load.py instead of just timerlat - the latter
sounds like you are changing the code of rtla-timerlat itself (in C)
rather than the example Python script. It is also recommended [1] to
use imperative mood in the commit messages, like this: "tools/rtla:
Improve code readability in timerlat_load.py" (and similarly for the
other patches).
[1] See the for submitting patches at
https://www.kernel.org/doc/html/latest/process/submitting-patches.html,
section Describe your changes.
Tomas
prev parent reply other threads:[~2024-10-21 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 20:01 [PATCH 1/3] tools/rtla: Code Cleanup and Readability Improvements for timerlat furkanonder
2024-10-21 8:19 ` Tomas Glozar [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='CAP4=nvR8CzLo1SdJJ67WjpMHGHzb35g1DRXeDPyENLmyvMLsQQ@mail.gmail.com' \
--to=tglozar@redhat.com \
--cc=furkanonder@protonmail.com \
--cc=linux-trace-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).