Re: [ANNOUNCE] 3.14-rt1

From: Mike Galbraith
Date: Wed Apr 30 2014 - 03:43:21 EST


On Tue, 2014-04-29 at 20:13 -0400, Steven Rostedt wrote:
> On Tue, 29 Apr 2014 07:21:09 +0200
> Mike Galbraith <umgwanakikbuti@xxxxxxxxx> wrote:
>
> > On Mon, 2014-04-28 at 16:37 +0200, Mike Galbraith wrote:
> >
> > > > Seems that migrate_disable() must be called before taking the lock as
> > > > it is done in every other location.
> > >
> > > And for tasklist_lock, seems you also MUST do that prior to trylock as
> > > well, else you'll run afoul of the hotplug beast.
> >
> > Bah. Futzing with dmesg while stress script is running is either a very
> > bad idea, or a very good test. Both virgin 3.10-rt and 3.12-rt with new
> > bugs squashed will deadlock.
> >
> > Too bad I kept on testing, I liked the notion that hotplug was solid ;-)
>
> I was able to stress cpu hotplug on 3.12-rt after applying the
> following patch.
>
> If there's no complaints about it. I'm going to add this to the 3.12-rt
> stable tree. As without it, it fails horribly with the cpu hotplug
> stress test, and I wont release a stable kernel that does that.

My local boxen are happy, 64 core box with 14-rt seems happy as well,
though I couldn't let it burn for long.

BTW, that dmesg business went into hiding. I didn't have time to put
virgin 10-rt back on and play around poking both kernels this that and
the other way again, but seems there's some phase-of-moon factor there.

-Mike

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/