Re: [ANNOUNCE] v4.11.12-rt13
From: Mike Galbraith
Date: Wed Oct 04 2017 - 12:08:14 EST
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
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
rtbox:/root # /opt/ltp/conformance/interfaces/timer_settime/timer_settime_5-2.run-test
signal was not sent