From: Mike Galbraith <bitbucket@online.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.6.6-rt17
Date: Fri, 21 Dec 2012 12:06:12 +0100 [thread overview]
Message-ID: <1356087972.4547.26.camel@marge.simpson.net> (raw)
In-Reply-To: <alpine.LFD.2.02.1211122223300.10000@ionos>
On Mon, 2012-11-12 at 22:28 +0100, Thomas Gleixner wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.6.6-rt17 release. 3.6.6-rt16 is just a
> not announced update release to 3.6.6.
>
> Changes since 3.6.6-rt16:
>
> * Finally make the NOHZ softirq pending detection work with the new
> softirq scheme.
Well, almost. They gripe when rebooting, but I haven't seen one other
than that. This is 3.6.11-rt23 on a 64 core DL980 I set up to run some
latency tests on.
[ 318.692463] kvm: exiting hardware virtualization
[ 319.568482] Disabling non-boot CPUs ...
[ 319.647819] NOHZ: local_softirq_pending 80
[ 319.876148] NOHZ: local_softirq_pending 202
[ 319.876172] NOHZ: local_softirq_pending 202
[ 319.988912] NOHZ: local_softirq_pending 282
[ 320.097066] NOHZ: local_softirq_pending 202
[ 320.321428] NOHZ: local_softirq_pending 80
[ 320.662601] NOHZ: local_softirq_pending 202
[ 320.662637] NOHZ: local_softirq_pending 202
[ 323.162636] NOHZ: local_softirq_pending 202
[ 323.162649] NOHZ: local_softirq_pending 202
[ 325.217675] Restarting system.
Don't suppose you know why LAZY_PREEMPT would make 3.0-rt explode if you
turn on wakeup_rt tracer do you?
I backported that and your softirq changes to 3.0. New softirq handling
scheme work spiffy there, LAZY_PREEMPT works fine too.. until you turn
tracing on, then it corrupts memory, and makes mushroom cloud.
-Mike
next prev parent reply other threads:[~2012-12-21 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 21:28 [ANNOUNCE] 3.6.6-rt17 Thomas Gleixner
2012-11-14 19:56 ` Fernando Lopez-Lezcano
2012-11-15 14:06 ` Paul Gortmaker
2012-11-15 18:11 ` Thomas Gleixner
2012-11-16 0:46 ` Fernando Lopez-Lezcano
2012-12-21 11:06 ` Mike Galbraith [this message]
2012-12-21 14:23 ` Thomas Gleixner
2012-12-21 15:49 ` 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=1356087972.4547.26.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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).