lkml.org 
[lkml]   [2015]   [Jul]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: mx6: suspicious RCU usage
On Tue, Jul 14, 2015 at 09:26:00AM -0700, Paul E. McKenney wrote:
> On Tue, Jul 14, 2015 at 01:06:32PM -0300, Fabio Estevam wrote:
> > Hi Paul,
> >
> > On Tue, Jul 14, 2015 at 1:00 PM, Paul E. McKenney
> > <paulmck@linux.vnet.ibm.com> wrote:
> >
> > > Does this patch help?
> > >
> > > https://lkml.org/lkml/2015/5/12/885
> >
> > I am using an ARM 32-bit machine, so I used this one instead:
> > https://lkml.org/lkml/2015/5/12/892
> >
> > , and it fixes the problem. Thanks!
> >
> > Feel free to add:
> >
> > Tested-by: Fabio Estevam <fabio.estevam@freescale.com>
>
> Glad it helped!
>
> Russell, did you want me to push this, or would you rather take it?

If it's the one I'm thinking of (using the generic code) because it
doesn't actually solve the problem we have. It may shut up the RCU
warning, but it doesn't solve the underlying problem - one which is
caused by the use of atomics (which use the exclusive instructions)
vs cache line migration between CPUs vs speculative prefetching...

It's possible right now that _dirty_ cache lines can be migrated to
the dying CPU, which are then lost on power down - and if we disable
the caches on the dying CPU, we then can't use exclusives, so atomics
(and all of the other normal kernel synchronisation mechanisms) are
out of the question.

--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.


\
 
 \ /
  Last update: 2015-07-14 23:01    [W:0.063 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site