Re: [PATCH 1/3] perf tools: Fix trace events storms due to weight demux

* Frederic Weisbecker wrote: > In case you wonder. This doesn't fix a regression so this is > 3.6 material. The newline and tracing one might be argued a regression, but yeah, these are probably best for v3.6. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH 1/3] perf tools: Fix trace events storms due to weight demux

In case you wonder. This doesn't fix a regression so this is 3.6 material. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http

[PATCH 1/3] perf tools: Fix trace events storms due to weight demux

Trace events have a period (weight) of 1 by default. This can be overriden on events definition by using the __perf_count() macro. For example, the sched_stat_runtime() is weighted with the runtime of the task that fired the event. By default, perf handles such weighted event by dividing it into