From: "Jorge Ramirez-Ortiz, Gmail" <jorge.ramirez.ortiz@gmail.com>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "Jorge Ramirez-Ortiz, Gmail" <jorge.ramirez.ortiz@gmail.com>,
"Schaffner, Tobias" <tobias.schaffner@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: Re: [libevl][PATCH 3/4] evl-test: Start evl-test with load by default
Date: Fri, 1 Nov 2024 19:13:42 +0100 [thread overview]
Message-ID: <ZyUaVn5UNfGB88TK@trux> (raw)
In-Reply-To: <87msiig9jm.fsf@xenomai.org>
On 01/11/24 18:15:25, Philippe Gerum wrote:
> "Jorge Ramirez-Ortiz, Gmail" <jorge.ramirez.ortiz@gmail.com> writes:
>
> >
> > [RFC]
> > I would like to update latmon[2] to the tip of Zephyr - it has fallen
> > behind - I'd like then to propose it upstream (if accepted I would like
> > to propose that it is removed from EVL). Anyone disagrees?
> >
>
> Fine by me.
>
> > IMO We should also take latmus to its own separate tree dedicated to RT
> > benchmarking and extend it to support scheduling latency metrics based
> > on GPIO data.
> > [\]
> >
>
> We would need to make it evl-agnostic then, assuming you want the latmus
> <-> latmon (Zephyr) combo to be broadly available off-the-shelf to
> others.
yes I think that would make sense. Xenomai3/EVL/PREEMPT_RT or any other linux-rt
could be easily compared with an off the shelf el-cheapo benchmarking tool.
>
> --
> Philippe.
next prev parent reply other threads:[~2024-11-01 18:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 13:45 [libevl][PATCH 0/4] evl-test: align with xeno-test Tobias Schaffner
2024-06-13 13:45 ` [libevl][PATCH 1/4] Copy dohell from Xenomai 3 Tobias Schaffner
2024-06-13 14:23 ` Philippe Gerum
2024-06-13 15:32 ` Jan Kiszka
2024-06-13 15:55 ` Philippe Gerum
2025-09-02 9:51 ` Jorge Ramirez-Ortiz, Gmail
2024-06-13 13:45 ` [libevl][PATCH 2/4] evl-test: Measure worst case latencies Tobias Schaffner
2024-06-13 14:09 ` Philippe Gerum
2024-06-13 13:45 ` [libevl][PATCH 3/4] evl-test: Start evl-test with load by default Tobias Schaffner
2024-06-13 14:16 ` Philippe Gerum
2024-06-13 15:30 ` Jan Kiszka
2024-06-13 16:09 ` Philippe Gerum
2024-11-01 17:00 ` Jorge Ramirez-Ortiz, Gmail
2024-11-18 7:48 ` Jan Kiszka
2024-11-18 8:26 ` Philippe Gerum
2025-09-01 18:46 ` Tobias Schaffner
2024-06-13 17:27 ` Philippe Gerum
2024-06-14 7:29 ` Jorge Ramirez-Ortiz, Gmail
2024-07-10 7:18 ` Tobias Schaffner
2024-10-24 20:00 ` Schaffner, Tobias
2024-10-27 19:13 ` Jorge Ramirez-Ortiz, Gmail
2024-11-01 16:55 ` Jorge Ramirez-Ortiz, Gmail
2024-11-01 17:15 ` Philippe Gerum
2024-11-01 18:13 ` Jorge Ramirez-Ortiz, Gmail [this message]
2025-09-03 5:29 ` Jan Kiszka
2025-09-03 8:12 ` Jorge Ramirez-Ortiz, Gmail
2025-09-03 8:20 ` Florian Bezdeka
2025-09-03 8:45 ` Jorge Ramirez-Ortiz, Gmail
2025-09-03 9:12 ` Florian Bezdeka
2024-06-13 13:45 ` [libevl][PATCH 4/4] evl-test: Add hectic for real-time stress Tobias Schaffner
2024-06-13 14:26 ` Philippe Gerum
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=ZyUaVn5UNfGB88TK@trux \
--to=jorge.ramirez.ortiz@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=rpm@xenomai.org \
--cc=tobias.schaffner@siemens.com \
--cc=xenomai@lists.linux.dev \
/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.