From: Tim Sander <tim@krieglstein.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: Bisect results for 4.4.1-rt[4,5]
Date: Wed, 17 Feb 2016 09:14:27 +0100 [thread overview]
Message-ID: <6333508.b5IKNpgbEX@dabox> (raw)
In-Reply-To: <56BDA0EF.7090503@linutronix.de>
Hi Sebastian
Am Freitag, 12. Februar 2016, 10:07:59 schrieben Sie:
...
> What about rt4? It is only the stable update so you should see here the
> numbers from rt3. If that is true and your numbers are stable it should
> be easy to run git bisect between rt4 and rt5. And looking at
> https://git.kernel.org/rt/linux-rt-devel/h/v4.4.1-rt5
> the only non-cosmetic change in -rt5 that should affect you is the
> migrate-disable fixup from Mike.
I have done a bisect run, its a rather innocent looking on liner which seems
to cause the problems. The numbers where reasonably stable so i am pretty
confident that this is the patch giving ~26µs additional latency on the Altera
SOC plattform:
eec2bf477ac674583a7d73b9d00f47c528b7266d is the first bad commit
commit eec2bf477ac674583a7d73b9d00f47c528b7266d
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: Thu Feb 4 16:38:10 2016 +0100
kernel/perf: mark perf_cpu_context's timer as irqsafe
Otherwise we get a WARN_ON() backtrace and some events are reported as
"not counted".
Cc: stable-rt@vger.kernel.org
Reported-by: Yang Shi <yang.shi@linaro.org>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Here are the numbers of the bisect run for reference:
==> g0dd3bdd <==
# Total: 100000000 099999829
# Min Latencies: 00010 00010
# Avg Latencies: 00020 00021
# Max Latencies: 00084 00101
# Histogram Overflows: 00000 00000
==> gbbc7819 <==
# Total: 100000000 099999798
# Min Latencies: 00010 00010
# Avg Latencies: 00021 00021
# Max Latencies: 00086 00091
# Histogram Overflows: 00000 00000
==> geec2bf4 <==
# Total: 099998713 100000000
# Min Latencies: 00010 00010
# Avg Latencies: 00020 00021
# Max Latencies: 00113 00070
# Histogram Overflows: 00000 00000
Best Regards
Tim
next prev parent reply other threads:[~2016-02-17 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 13:56 [ANNOUNCE] 4.1.5-rt5 Sebastian Andrzej Siewior
2016-02-12 8:28 ` Tim Sander
2016-02-12 9:07 ` Sebastian Andrzej Siewior
2016-02-12 14:36 ` [ANNOUNCE] 4.1.5-rt5 meant to reply to 4.4.1-rt5 Tim Sander
2016-02-17 8:14 ` Tim Sander [this message]
2016-02-25 14:06 ` Bisect results for 4.4.1-rt[4,5] Sebastian Andrzej Siewior
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=6333508.b5IKNpgbEX@dabox \
--to=tim@krieglstein.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 NNTP newsgroup(s).