From: Florian Weimer <fweimer@redhat.com>
To: Stefan Liebler via Libc-alpha <libc-alpha@sourceware.org>
Cc: Stefan Liebler <stli@linux.ibm.com>
Subject: Re: [PATCH] Loosen the limits of time/tst-cpuclock1.
Date: Fri, 28 Aug 2020 14:29:45 +0200 [thread overview]
Message-ID: <87d03brm12.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20200828085852.1861153-1-stli@linux.ibm.com> (Stefan Liebler via Libc-alpha's message of "Fri, 28 Aug 2020 10:58:52 +0200")
* Stefan Liebler via Libc-alpha:
> Starting with the commit 04deeaa9ea74b0679dfc9d9155a37b6425f19a9f "Fix
> time/tst-cpuclock1 intermitent failures" (2020-07-11), this test fails
> quite often on s390x/s390 with one/multiple of those: "before - after"
> / "nanosleep time" / "dead - after" ourside reasonable range.
How much value do these cpuclock tests actually have? Maybe we should
just remove them, given that their test objective is so difficult to
model in current execution environments.
Maybe we could measure clock discontinuities on the CPU-burning thread
and detect CPU stealing this way. But I'm not sure if this would be
worth it.
Thanks,
Florian
next prev parent reply other threads:[~2020-08-28 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 8:58 Stefan Liebler
2020-08-28 12:29 ` Florian Weimer [this message]
2020-08-31 12:57 ` Lucas A. M. Magalhaes
2020-08-31 12:59 ` Florian Weimer
2020-09-02 16:10 ` Stefan Liebler
2020-09-21 11:28 ` Florian Weimer
2020-09-29 13:53 ` Lucas A. M. Magalhaes
2020-09-29 14:01 ` Adhemerval Zanella
2020-09-29 17:22 ` Carlos O'Donell
2020-09-30 11:48 ` Adhemerval Zanella
2020-10-19 14:48 ` Stefan Liebler
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=87d03brm12.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=stli@linux.ibm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).