From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: "Ahmet Cevdet Çelik" <ahmetcevdet006@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: VIS, a small Linux/x86_64 tool for CPU jitter, SMI evidence, and runtime placement reports
Date: Fri, 15 May 2026 21:59:00 +0200 [thread overview]
Message-ID: <agd7BPZKZN8c8gud@lx-t490> (raw)
In-Reply-To: <77cb843a-d5fc-4a35-b0d7-2b0c7f2f24d3@gmail.com>
On Thu, 14 May 2026, Ahmet Cevdet Çelik wrote:
>
> I would appreciate technical feedback from the Linux RT community,
> especially on these questions:
>
> 1. Is this kind of evidence/reporting layer useful next to existing
> tools such as cyclictest, hwlatdetect, rtla, ftrace, and perf?
...
> 3. Should VIS try to import or align with rtla/hwlat/perf data rather
> than implementing more sensors itself?
>
> 4. What would be the most useful next step for making this relevant to
> real-time Linux users? For example:
> - better integration with rtla/hwlat,
...
> I am not looking to make exaggerated claims. The project is early, and
> I would rather get criticism now than build in the wrong direction.
>
I would personally recommend that you add the missing bits to the existing
official tools instead: rtla, ftrace, perf, etc.
By submitting your new additions there, you will also get feedback from the
experts on each topic.
Random personal GitHub projects really die off after a while.
All the best,
Ahmed
prev parent reply other threads:[~2026-05-15 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 9:02 VIS, a small Linux/x86_64 tool for CPU jitter, SMI evidence, and runtime placement reports Ahmet Cevdet Çelik
2026-05-15 19:59 ` Ahmed S. Darwish [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=agd7BPZKZN8c8gud@lx-t490 \
--to=darwi@linutronix.de \
--cc=ahmetcevdet006@gmail.com \
--cc=linux-rt-users@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.