Messages in this thread | | | Date | Wed, 7 Mar 2007 16:40:13 -0800 | From | "Luong Ngo" <> | Subject | Re: Sleeping thread not receive signal until it wakes up |
| |
On 3/7/07, Lee Revell <rlrevell@joe-job.com> wrote: > On 3/7/07, linux-os (Dick Johnson) <linux-os@analogic.com> wrote: > > Interruptible_sleep_on is interruptible, but for your task to > > actually be awakened and your alarm handler to get some CPU, > > it needs to be scheduled. If the BKL (big kernel lock) is > > held, it won't be scheduled until it is released. > > You can schedule while holding the BKL and it will be dropped and reacquired. > > Lee >
My hardware is PowerPC architecture. Does it have any thing to do with the kernel locking? Also, I saw CONFIG_LOCK_KERNEL, CONFIG_PREEMPT_BKL ans CONFIG_SMP in the file include/linux/smp_lock.h, or CONFIG_PREEMPT in lib/kernel_lock.c and I don't have any of these macro defined, would that be the reason. I could not find where these option when running make menuconfig either.
Thanks, LNgo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |