On Tue, 1 Mar 2016 09:45:05 -0500
Steven Rostedt wrote:
> On Sat, 27 Feb 2016 11:32:06 +0100
> Sebastian Andrzej Siewior wrote:
>
> > On 2016-02-26 16:32:42 [-0500], Steven Rostedt wrote:
> > > 3.18.27-rt26-rc1 stable review patch.
> > > If anyone has any objections, please let me know.
>
On Sat, 27 Feb 2016 11:32:06 +0100
Sebastian Andrzej Siewior wrote:
> On 2016-02-26 16:32:42 [-0500], Steven Rostedt wrote:
> > 3.18.27-rt26-rc1 stable review patch.
> > If anyone has any objections, please let me know.
>
> Please merge this one along with "kernel: migrate_disable() do fastpat
On Mon, 29 Feb 2016, Steven Rostedt wrote:
> On Sat, 27 Feb 2016 11:32:06 +0100
> Sebastian Andrzej Siewior wrote:
>
> > On 2016-02-26 16:32:42 [-0500], Steven Rostedt wrote:
> > > 3.18.27-rt26-rc1 stable review patch.
> > > If anyone has any objections, please let me know.
> >
> > Please mer
On Sat, 27 Feb 2016 11:32:06 +0100
Sebastian Andrzej Siewior wrote:
> On 2016-02-26 16:32:42 [-0500], Steven Rostedt wrote:
> > 3.18.27-rt26-rc1 stable review patch.
> > If anyone has any objections, please let me know.
>
> Please merge this one along with "kernel: migrate_disable() do fastpat
On 2016-02-26 16:32:42 [-0500], Steven Rostedt wrote:
> 3.18.27-rt26-rc1 stable review patch.
> If anyone has any objections, please let me know.
Please merge this one along with "kernel: migrate_disable() do fastpath
in atomic & irqs-off". Otherwise we might get recursive with lockdep and
CPU-hot
3.18.27-rt26-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
I see here large latencies during a stack dump on x86. The
preempt_disable() and get_cpu() should forbid moving the task to another
CPU during a stack dump
6 matches
Mail list logo