Re: [RFC][PATCH 06/11] sched: Fix trace_sched_switch()

From	Steven Rostedt <rostedt@goodmis.org>
Newsgroups	linux.kernel
Subject	Re: [RFC][PATCH 06/11] sched: Fix trace_sched_switch()
Date	2015-09-29 18:40 +0200
Message-ID	<qe66E-3vi-47@gated-at.bofh.it> (permalink)
References	<qdZHQ-2IS-3@gated-at.bofh.it> <qdZHQ-2IS-25@gated-at.bofh.it> <qe5az-2aq-53@gated-at.bofh.it> <qe5tU-2x8-23@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, 29 Sep 2015 17:48:28 +0200
Peter Zijlstra <peterz@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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[RFC][PATCH 06/11] sched: Fix trace_sched_switch() Peter Zijlstra <peterz@infradead.org> - 2015-09-29 11:50 +0200
  Re: [RFC][PATCH 06/11] sched: Fix trace_sched_switch() Steven Rostedt <rostedt@goodmis.org> - 2015-09-29 17:40 +0200
    Re: [RFC][PATCH 06/11] sched: Fix trace_sched_switch() Peter Zijlstra <peterz@infradead.org> - 2015-09-29 18:00 +0200
      Re: [RFC][PATCH 06/11] sched: Fix trace_sched_switch() Steven Rostedt <rostedt@goodmis.org> - 2015-09-29 18:40 +0200

csiph-web