From: Mike Galbraith <efault@gmx.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v4.11.12-rt13
Date: Fri, 06 Oct 2017 19:38:08 +0200 [thread overview]
Message-ID: <1507311488.5480.20.camel@gmx.de> (raw)
In-Reply-To: <1507296802.6364.14.camel@gmx.de>
On Fri, 2017-10-06 at 15:33 +0200, Mike Galbraith wrote:
>
> I'll run full ltp again, make sure there are no new failure deltas.
Haven't done that yet, but I have checked all of the reported failures.
time-hrtimer:-Use-softirq-based-wakeups-for-non-RT-threads.patch fixes
clock_settime_8-1.run-test, hrtimer:-Update-offset-for-soft-bases.patch
fixes the rest.
However...
homer:..debug/tracing # /usr/local/ltp/conformance/interfaces/clock_settime/clock_settime_8-1.run-test
Test PASSED
homer:..debug/tracing # chrt -f 1 /usr/local/ltp/conformance/interfaces/clock_settime/clock_settime_8-1.run-test
Ended too late. 1507308976 >> 1507308974
Test FAILED
That's a bit troubling. No earlier kernel, rt or not, cares about
policy. Either now getting a NAK is less than wonderful, but
SCHED_FIFO gets a NAK while SCHED_OTHER walks away with an ACK?
-Mike
next prev parent reply other threads:[~2017-10-06 17:38 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
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 [this message]
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=1507311488.5480.20.camel@gmx.de \
--to=efault@gmx.de \
--cc=anna-maria@linutronix.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 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).