> With these changes (patch appended), I was able to compile and debug my
> spinlocks. One problem remains, though:
> sched.c:80111e71: spin_lock(sched.c:801ce964) already locked
> is displayed a number of times, and I didn't spend enough time to track this
> one down.
there is a tricy issue here:
ret_from_smpfork:
GET_CURRENT(%ebx)
btrl $0, SYMBOL_NAME(scheduler_lock)
i suppose you have not addded debugging code to entry.S?
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu