Linux Trace Kernel
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <Usama.Anjum@collabora.com>
To: Daniel Wagner <wagi@monom.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Daniel Bristot de Oliveira <bristot@kernel.org>
Cc: Usama.Anjum@collabora.com, kernel@collabora.com,
	gustavo.padovan@collabora.com, helen.koike@collabora.com
Subject: [Report] rtla: Failed to set runtime and/or period
Date: Thu, 12 Sep 2024 18:58:02 +0500	[thread overview]
Message-ID: <d3468fce-088c-45d0-8543-a2bc9fef07c9@collabora.com> (raw)

Hi,

We are running rt-tests on KernelCI. I'm looking at failures and I found
out that rtla osnoise and rtla timerlat are failing. We have just
enabled these tests and they are failing from day one.

The first thing I fixed in my local setup is to sync the version of rtla
with that of the running kernel from the source. It resolves the Tracer
timerlat not found!" error as we had installed the older rtla package
from Debian on CI. I'll update it. Is the version of rtla dependent on
the exact kernel version or any recent rtla version is acceptable?

The other errors are persistent:

➜  sudo ./rtla osnoise hist -r 900000
Failed to set runtime and/or period
Could not apply config

I thought maybe some argument are wrong. I ran the example from man page:

➜  sudo ./rtla osnoise hist -P F:1 -c 0-11 -r 900000 -d 1M -b 10 -E 25
Failed to apply CPUs config
Could not apply config

Is there some configuration which is missing for running rtla? Please
let me know.

-- 
BR,
Muhammad Usama Anjum

             reply	other threads:[~2024-09-12 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 13:58 Muhammad Usama Anjum [this message]
2024-09-13 13:47 ` [Report] rtla: Failed to set runtime and/or period Daniel Wagner
2024-09-16  5:33   ` Muhammad Usama Anjum

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=d3468fce-088c-45d0-8543-a2bc9fef07c9@collabora.com \
    --to=usama.anjum@collabora.com \
    --cc=bristot@kernel.org \
    --cc=gustavo.padovan@collabora.com \
    --cc=helen.koike@collabora.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=wagi@monom.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