Messages in this thread | | | Date | Wed, 10 Nov 2004 00:20:02 +0100 | From | Ingo Molnar <> | Subject | Re: [patch] Real-Time Preemption, -RT-2.6.10-rc1-mm3-V0.7.23 |
| |
* Mark_H_Johnson@raytheon.com <Mark_H_Johnson@raytheon.com> wrote:
> [3] I am not so sure that the latency tracing works. I do not get any > trace output, even if I set preempt_max_latency to zero.
What is the value of preempt_thresh? If it's set then it overrides the preempt_max_latency value. (previously the bogus timing values probably triggered even a relatively high preempt-threshold, but now with a correct tracer it's not possible anymore.)
> [...] I also noticed that /proc/sys/kernel/preempt_wakeup_timing was > removed at .20 but not sure if that was deliberate. [...]
yeah, this was deliberate - it's a side-effect of separating it from the other timing options.
Ingo - 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/
| |