On Tue, 2009-03-24 at 12:44 +0100, Frederic Weisbecker wrote: > As I explained in my previous mail, you trace is only > a snapshot that happened in 10 msec. > > I experimented different sizes for the ring buffer but even > a 1 second trace require 20 Mo of memory. And a so huge trace > would be impractical. > > I think we should keep the trace filters we had previously. > If you don't minde, could you please retest against latest -tip > the following updated patch? Iadded the filters, fixed the python > subshell and also flushed the buffer more nicely according to > a recent feature in -tip: > > echo > trace > > instead of switching to nop. > You will need to pull latest -tip again. Ok, new set of traces uploaded again here: http://disenchant.net/tmp/bug-12465/trace-4/ These were taken using 2.6.29-tip-02749-g398bf09. Same as last time, it was only necessary to have the one guest running to reproduce the problem. Cheers, Kevin. -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
