[lkml]   [2008]   [Aug]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] seqlock: serialize against writers
On Fri, Aug 29, 2008 at 12:29:42PM -0400, Gregory Haskins wrote:
> Andi Kleen wrote:
> >> Im running it on a x86_64 box as we speak. How can I tell if there is a
> >> certain mode that is permitting this?
> >>
> >
> > If the boot up says you're running with PMtimer then it uses the fallback
> > (usually happens on pre Fam10h AMD boxes). A typical Intel box
> > would use the faster ring 3 only TSC path and then explode with your
> > change I bet.
> >
> Thinking about this some more, perhaps the issue is I am not hitting the
> contended path in vsyscall?

Yes it will be only contended when gettimeofday() races with the timer
interrupt. You could try to run gettimeofday() in a loop and see how
long it holds up.

But anyways from the theory you should crash when it happens.
Writes to kernel data are not allowed in vsyscalls and your read_lock clearly
does a write.



 \ /
  Last update: 2008-08-29 18:37    [W:0.037 / U:4.408 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site