public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <a.darwish@linutronix.de>
To: Punit Agrawal <punit1.agrawal@toshiba.co.jp>
Cc: jkacur@redhat.com, binh1.tranhai@toshiba.co.jp,
	Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>,
	dwagner@suse.de, linux-rt-users@vger.kernel.org
Subject: Re: Some issues running rteval on arm64, arm and i386
Date: Fri, 22 Jan 2021 07:26:41 +0100	[thread overview]
Message-ID: <YApwIRJdMCXcMVbU@lx-t490> (raw)
In-Reply-To: <877doa1uwx.fsf@kokedama.swc.toshiba.co.jp>

On Mon, Jan 18, 2021 at 06:00:46PM +0900, Punit Agrawal wrote:
>
> We ran into a few issues when trying to run rteval on arm64, arm and
> i386.
>
> A few of the assumptions in rteval don't hold true on these systems.
>

For some embedded devices, it can be tough to use rteval with it. In
general, it requires, *on the target*:

  1. a full development toolchain (GCC, make, flex, bison, etc.)
  2. a full kernel source tree
  3. a full Python environment

You can use a combination of stress-ng and cyclictest to properly
evaluate your preempt_rt system latencies. Just make sure to exclude the
stress-ng stressors which allocate real-time threads, which can (and do)
conflict with the cyclictest ones.

Kind regards,

--
Ahmed S. Darwish

  reply	other threads:[~2021-01-22  6:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18  9:00 Some issues running rteval on arm64, arm and i386 Punit Agrawal
2021-01-22  6:26 ` Ahmed S. Darwish [this message]
2021-01-22 23:31   ` John Kacur
2021-01-26  1:40     ` Punit Agrawal
2021-01-22 23:27 ` John Kacur
2021-01-26  1:04   ` Punit Agrawal

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=YApwIRJdMCXcMVbU@lx-t490 \
    --to=a.darwish@linutronix.de \
    --cc=binh1.tranhai@toshiba.co.jp \
    --cc=daniel.sangorrin@toshiba.co.jp \
    --cc=dwagner@suse.de \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=punit1.agrawal@toshiba.co.jp \
    /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