Messages in this thread | | | Subject | Re: [ANNOUNCE] 2.6.15-rc5-hrt2 - hrtimers based high resolution patches | From | Steven Rostedt <> | Date | Wed, 14 Dec 2005 09:04:38 -0500 |
| |
On Wed, 2005-12-14 at 08:48 -0500, Steven Rostedt wrote:
> And going into gdb, I get: > > (gdb) li *0xc0136b98 > 0xc0136b98 is in hrtimer_cancel (kernel/hrtimer.c:671). > 666 int hrtimer_cancel(struct hrtimer *timer) > 667 { > 668 for (;;) { > 669 int ret = hrtimer_try_to_cancel(timer); > 670 > 671 if (ret >= 0) > 672 return ret; > 673 } > 674 } > 675 > > So it may not really be locked, and if I waited a couple of hours, it > might actually finish (the test usually takes a couple of minutes to > run, and I let it run here for about 20 minutes).
Nope, looking at my test code again, I forgot that I set the program to max prio, so this would never finish.
-- Steve
- 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/
| |