On Fri, 8 Feb 2019, Thomas Gleixner wrote: > Will, > > On Fri, 8 Feb 2019, Will Deacon wrote: > > On Fri, Dec 07, 2018 at 05:53:21PM +0000, Will Deacon wrote: > > > Anyway, moving the counter read into the protected region is a little fiddly > > > because the memory barriers we have in there won't give us the ordering we > > > need. We'll instead need to do something nasty, like create a dependency > > > from the counter read to the read of the seqlock: > > > > > > Maybe the untested crufty hack below, although this will be a nightmare to > > > implement in C. How is the in kernel ktime_get() correctness guaranteed then? Thanks, tglx
