Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables

2008-07-21 Thread Chirag Jog
Hi Benjamin * Benjamin Herrenschmidt <[EMAIL PROTECTED]> [2008-07-19 08:05:30]: > > > With the original patch, the pending batch does get flushed > > in a non-preemptable region. > > I am resending the original with just adding the necesary comments. > > Your comment isn't what I meant. What

Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables

2008-07-18 Thread Chirag Jog
* Benjamin Herrenschmidt <[EMAIL PROTECTED]> [2008-07-18 06:14:31]: > > > All these operations are done assuming that tlb_gather_mmu disables > > preemption and tlb_finish_mmu enables preemption again. > > This is not true for -rt. > > For x86, none of the code paths between tlb_gather_mmu and >

Re: [PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables

2008-07-17 Thread Chirag Jog
Hi Benjamin, Thanks for the review * Benjamin Herrenschmidt <[EMAIL PROTECTED]> [2008-07-15 11:32:01]: > On Wed, 2008-07-09 at 21:35 +0530, Chirag Jog wrote: > > Hi, > > This patch fixes various paths in the -rt kernel on powerpc64 where per_cpu > > variables are a

[PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables

2008-07-09 Thread Chirag Jog
Hi, This patch fixes various paths in the -rt kernel on powerpc64 where per_cpu variables are accessed in a preempt unsafe way. When a power box with -rt kernel is booted, multiple BUG messages are generated "BUG: init:1 task might have lost a preemption check!". After booting a kernel with these

[PATCH][RT][PPC64] Fix preempt unsafe paths accessing per_cpu variables

2008-07-09 Thread Chirag Jog
Hi, This patch fixes various paths in the -rt kernel on powerpc64 where per_cpu variables are accessed in a preempt unsafe way. When a power box with -rt kernel is booted, multiple BUG messages are generated "BUG: init:1 task might have lost a preemption check!". After booting a kernel with these

Re: [PATCH] [POWERPC] Use a sensible default for clock_getres() in the vdso.

2008-02-05 Thread Chirag Jog
I tried this patch. It seems to solve the reported problem and give a 1ns resolution. Thanks. -- Cheers, Chirag Jog ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev