All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] [RFC] syscalls/perf_event_open02: Fix failures
Date: Thu, 3 May 2018 10:49:31 +0200	[thread overview]
Message-ID: <20180503084931.GE29568@rei> (raw)
In-Reply-To: <20180424124957.15634-1-chrubis@suse.cz>

Hi!
> The testcase was failing randomly, it could be reproduced easily when
> the machine is under load. To reproduce the issue just run a few
> dd if=/dev/zero of=/dev/null to saturate your CPUs.
> 
> It has been sugessted that the reason for the failure are rounding
> errors caused by a frequent preemption. I haven't got a definitive
> answer from kernel devs for this but it's true that changing the process
> pritority to realtime SCHED_FIFO for the measurement does fix the issue.
> 
> So we either delete the test or apply this patch.

Any comments for this patch?

I would like to have this sorted out before the release...

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2018-05-03  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 12:49 [LTP] [PATCH] [RFC] syscalls/perf_event_open02: Fix failures Cyril Hrubis
2018-05-03  8:49 ` Cyril Hrubis [this message]
2018-05-11 11:48   ` Cyril Hrubis
2018-05-14 10:09 ` Cyril Hrubis

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=20180503084931.GE29568@rei \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.