All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re: [Dovetail] x86 test version available (kernel v5.10)
Date: Mon, 15 Feb 2021 18:07:48 +0100	[thread overview]
Message-ID: <871rdhjm3f.fsf@xenomai.org> (raw)
In-Reply-To: <d3aadb22-6426-5326-31ed-fb44ee2a31aa@siemens.com>


Jan Kiszka <jan.kiszka@siemens.com> writes:

> On 15.02.21 14:28, Jan Kiszka wrote:
>> Now the next issue is
>> 
>> /usr/lib/xenomai/testsuite/smokey: test sched_quota failed: Protocol error
>> sched-quota.c:332, out of quota: 13.7%
>> (on a real target, an Atom-class box).
>> 
>
> Testsuite issue, long pending:
>
> https://gitlab.denx.de/Xenomai/xenomai/-/blob/master/testsuite/smokey/sched-quota/sched-quota.c#L204
>
> Those pthread_kill() in the loop will kick the caller into non-rt, while
> it is not yet done with collecting the loop counters from the other
> workers. Result is pure random, sometimes still within the defined
> limits, but sometimes reporting false overruns.

Make sense, we need to collect the counters independently then.

>
> No idea what those signal submissions supposed to do - test runs and
> terminates fine without them as well.
>

On SMP probably, on UP I don't think so, because if you don't demote the
workers, then the following call to pthread_cancel() will switch the
main context out of primary mode, leaving one of the workers preempt
back, then go spinning full speed, locking the CPU (there is no
condition for exiting the work loop).

Using the throttling hack like the calibration loop does may help (I
guess I overlooked this back then).


-- 
Philippe.


  parent reply	other threads:[~2021-02-15 17:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 16:06 [Dovetail] x86 test version available (kernel v5.10) Philippe Gerum
2021-02-01 17:32 ` Jan Kiszka
2021-02-03 17:35   ` Philippe Gerum
2021-02-06 12:29     ` Jan Kiszka
2021-02-06 17:23       ` Philippe Gerum
2021-02-15 13:28       ` Jan Kiszka
2021-02-15 15:11         ` Jan Kiszka
2021-02-15 16:53           ` Jan Kiszka
2021-02-15 17:19             ` Jan Kiszka
2021-02-15 17:07           ` Philippe Gerum [this message]
2021-02-15 17:21             ` Philippe Gerum
2021-02-22 15:35 ` Henning Schild
2021-02-22 17:59   ` Henning Schild
2021-03-11 16:35   ` Henning Schild
2021-03-12  7:22     ` Jan Kiszka
2021-03-12 11:32       ` Jan Kiszka
2021-03-12 18:18         ` Henning Schild
2021-03-12 19:46           ` Henning Schild
2021-03-12 19:53             ` Henning Schild
2021-03-15  7:57               ` Jan Kiszka

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=871rdhjm3f.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.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.