From: Philippe Gerum <rpm@xenomai.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: xenomai@lists.linux.dev, Jan Kiszka <jan.kiszka@siemens.com>,
Tobias Schaffner <tobias.schaffner@siemens.com>
Subject: Re: EVL 7.1 and below on armhf: System hang when running the testsuite under stress
Date: Tue, 23 Jun 2026 14:30:54 +0200 [thread overview]
Message-ID: <87pl1he8w1.fsf@xenomai.org> (raw)
In-Reply-To: <87v7b9e9if.fsf@xenomai.org> (Philippe Gerum's message of "Tue, 23 Jun 2026 14:17:28 +0200")
Philippe Gerum <rpm@xenomai.org> writes:
> Florian Bezdeka <florian.bezdeka@siemens.com> writes:
>
>>>
>>> Since r58, we have the running_on_vm() predicate available to test code,
>>> which checks whether the "EVL_ON_VM" environment variable is set to
>>> 1/y/yes/Y/YES (unfortunately, I'm not aware of any way to detect this
>>> without user input like the valgrind vm allows via some hypercall).
>>
>> systemd-detect-virt implements a couple of mechanisms to detect a lot of
>> different hypervisors. Could we depend on it?
>>
>
> Yes, running_on_vm() could try this source if present, falling back to
> the envvar method if not.
Actually, having evl-test feed EVL_ON_VM would be better. This way we
could still control the vm detection by setting EVL_ON_VM as desired
before running the test manually (i.e. without evl-test). I'm preparing
a patch for this.
--
Philippe.
prev parent reply other threads:[~2026-06-23 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 7:29 EVL 7.1 and below on armhf: System hang when running the testsuite under stress Florian Bezdeka
2026-06-22 9:21 ` Philippe Gerum
2026-06-22 22:30 ` Florian Bezdeka
2026-06-23 8:18 ` Tobias Schaffner
2026-06-23 12:17 ` Philippe Gerum
2026-06-23 12:30 ` Philippe Gerum [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=87pl1he8w1.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--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.