On Tue, 29 Sep 2015 17:48:28 +0200 Peter Zijlstra <pet...@infradead.org> wrote:
> /SHOULD/ being the operative word. Experience has taught me that > changing the sched tracepoint leads to borkage. Right. But experience also tells us that those relying on offsets will get brokage if they run 32 bit userspace on a 64 bit kernel too. > > But we can sure try, see if someone notices etc.. Same with > trace_sched_wakeup(), that still prints a dummy value. Removing a field can break things that even use the parsing library. That's why we still have that. -- Steve -- 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/
