On Thu, 2005-12-29 at 09:22 +0100, Ingo Molnar wrote:
> * Lee Revell <[email protected]> wrote:
> > I'm not sure how much work it would be to break out
> > CONFIG_LATENCY_TRACE as a separate patch.
> could you check out the 2.6.15-rc7 version of the latency tracer i
> uploaded to:
> could test it by e.g. trying to reproduce the same VM latency as in the
> -rt tree. [the two zlib patches are needed if you are using 4K stacks,
> mcount increases stack footprint.]
Would you mind submitting this for 2.6.16? We already have one case
where it would have caught a regression in time for 2.6.15, so IMHO this
would be a great addition to "Kernel hacking".
I have had absolutely no problems running this with 2.6.15-rc7, it works
perfectly, as it has in the -rt tree for ages.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Video 4 Linux]
[Linux for the blind]