All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinicius Marques <viniciusmarkar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Real-time Linux Analysis tool
Date: Sat, 6 Sep 2025 09:32:13 -0300	[thread overview]
Message-ID: <cce59d13-e8ac-4573-b0ff-4f211eba07ce@gmail.com> (raw)

I'm using Google Translation; please bear with the team if anything is a 
little out of context in this email.

Hello, my name is Vinicius. I'm studying the Linux Kernel documentation 
and am now in the Rtla section. I started reading about this tool, and 
from the very beginning, I decided to put its usefulness into practice. 
On my first attempt using the Rtla osnoise command on my computer via 
the terminal, I could clearly see it in action. The point and the reason 
for being here now is to be able to initiate contact with you here and 
share important facts about the practical use of this Rtla tool in the 
daily life of an average user like myself. I decided to open this 
connection with you here through this email. When I first put Rtla into 
practice using Rtla osnoise, my computer started experiencing small, 
repetitive and constant crashes, making it very difficult for me to 
manage computing resources and continue using the Rtla tool. The core of 
this report is that my intention is to pass on this knowledge to the 
Rtla technical team. Why is this report important? This report is 
important because the Rtla technical team can begin to gain a more 
comprehensive understanding of the use of this fantastic Rtla tool in 
the practical field of the average user and also in organizations and 
companies. The central question here is: what can be done to reduce the 
impact of minor crashes caused by the use of Rtla? I am available to 
interact with the team. I wish the entire team a great work day. Thank 
you for receiving this email. I await your response and I am rooting for 
the team. Thank you.


                 reply	other threads:[~2025-09-06 12:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cce59d13-e8ac-4573-b0ff-4f211eba07ce@gmail.com \
    --to=viniciusmarkar@gmail.com \
    --cc=linux-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 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.