> I really don't want the multi-buffer nonsense proposed. > An event gets > _1_ buffer, that's it.
But we already have multi buffer. Just profile multiple CPUs Then you have one buffer per CPU that need to be combined. This just has two buffers per CPU. > That also means that if someone redirect another event into this buffer, > it needs to just work. All the tools already handle multiple buffers (for multi CPUs). So they don't need it. > And because its a perf buffer, people expect it to look like one. So > we've got 'wrap' it. Flushing TLBs from NMIs or irq work or any interrupt context is just a non starter. The start/stop hardware and create gigantic gaps was also pretty bad and would completely change the perf format too It seem to me you're trying to solve a non-problem. -Andi -- a...@linux.intel.com -- Speaking for myself only -- 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://www.tux.org/lkml/
