Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1675608 > unrolled thread

Re: [PATCHv5] arm64/cpufeature: don't use mutex in bringup path

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCHv5] arm64/cpufeature: don't use mutex in bringup path Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2017-06-27 14:10 +0200
    Re: [PATCHv5] arm64/cpufeature: don't use mutex in bringup path Mark Rutland <mark.rutland@arm.com> - 2017-06-29 16:20 +0200

#1675608 — Re: [PATCHv5] arm64/cpufeature: don't use mutex in bringup path

On 2017-05-17 17:05:31 [+0100], Catalin Marinas wrote:
> > Catalin, can you take this as a fix for v4.12?
> 
> I queued it for 4.12-rc2. Thanks.

I backported a few patches into v4.11-RT and the backtrace popped up
(which is fixed by this patch). The problem existed before it has been
made visible. Do you intend to push this patch stable?

Sebastian

[toc] | [next] | [standalone]

#1677786

Hi,

On Tue, Jun 27, 2017 at 02:05:55PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-05-17 17:05:31 [+0100], Catalin Marinas wrote:
> > > Catalin, can you take this as a fix for v4.12?
> > 
> > I queued it for 4.12-rc2. Thanks.
> 
> I backported a few patches into v4.11-RT and the backtrace popped up
> (which is fixed by this patch). The problem existed before it has been
> made visible. Do you intend to push this patch stable?

I wasn't planning to.

This was fairly invasive (so there'd be a number of conflicts to fix
up), and we weren't seeing issues in practice for !RT kernels.

If this is causing ap roblem in practice for !RT, I'd be happy to.

Thanks,
Mark.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web