From: Mike Galbraith <efault@gmx.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v4.11.12-rt13
Date: Wed, 04 Oct 2017 18:07:59 +0200 [thread overview]
Message-ID: <1507133279.6934.66.camel@gmx.de> (raw)
In-Reply-To: <20170905145244.jro4jywfxugmn7eh@linutronix.de>
On Tue, 2017-09-05 at 16:52 +0200, Sebastian Andrzej Siewior wrote:
> Dear RT folks!
>
> I'm pleased to announce the v4.11.12-rt13 patch set.
>
> Changes since v4.11.12-rt12:
>
> - Merging Anna-Maria's "hrtimer: Provide softirq context hrtimers"
> series. Merging this series enables the removal of almost all
> hrtimer related patches in the queue. What is left is the "force
> switch" of all timers to the softirq context (except a few special
> ones) and a wait-queue to wait until a timer is completed.
> The overall diffstat compared to -rt12 is
> 21 files changed, 573 insertions(+), 651 deletions(-)
> amazing. We have RT wise the same functionality with 78 lines less
> of code.
(post lazy sod mode [vacation] testing...)
Seems combo-patch induced some ltp posix conformance test grumbling.
+clock_settime_8_1 ... ... FAILED
+clock_settime_4_2 ... ... FAILED
+clock_settime_speculative_4_3 ... ... FAILED
+timer_settime_5_2 ... ... FAILED
+timer_settime_5_1 ... ... FAILED
+timer_settime_5_3 ... ... FAILED
rtbox:/root # /usr/local/ltp/conformance/interfaces/clock_settime/clock_settime_8-1.run-test
Ended too late. 1507131910 >> 1507131908
Test FAILED
rtbox:/root # /usr/local/ltp/conformance/interfaces/clock_settime/clock_settime_4-2.run-test
timer should have expired _immediately_
rtbox:/root # /usr/local/ltp/conformance/interfaces/clock_settime/speculative/clock_settime_speculative_4-3.run-test
Overrun count =0, not # of repeating timer expirys
FAIL: Caught 0 signals, not 1
Test FAILED
rtbox:/root # /opt/ltp/conformance/interfaces/timer_settime/timer_settime_5-2.run-test
signal was not sent
next prev parent reply other threads:[~2017-10-04 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 14:52 [ANNOUNCE] v4.11.12-rt13 Sebastian Andrzej Siewior
2017-10-04 16:07 ` Mike Galbraith [this message]
2017-10-05 15:54 ` Sebastian Andrzej Siewior
2017-10-06 2:20 ` Mike Galbraith
2017-10-06 10:28 ` Sebastian Andrzej Siewior
2017-10-06 13:33 ` Mike Galbraith
2017-10-06 17:38 ` Mike Galbraith
2017-10-07 4:50 ` Mike Galbraith
2017-10-10 16:24 ` Sebastian Andrzej Siewior
2017-10-10 16:47 ` Sebastian Andrzej Siewior
2017-10-10 17:27 ` Mike Galbraith
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=1507133279.6934.66.camel@gmx.de \
--to=efault@gmx.de \
--cc=bigeasy@linutronix.de \
--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 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.