LKML Archive on
help / color / mirror / Atom feed
From: Cong Wang <>
To: Peter Zijlstra <>
Cc: Ivan Babrou <>,
	LKML <>, Paul Turner <>,
	Mike Galbraith <>,
	Thomas Gleixner <>,
	Ingo Molnar <>
Subject: Re: [PATCH 3/3] sched/fair: add tracepoints for cfs throttle
Date: Thu, 24 May 2018 15:23:28 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, May 24, 2018 at 12:11 AM, Peter Zijlstra <> wrote:
> The problem with tracepoints is that they can become ABI and you cannot
> change them without breaking tools. This is a crap situation and I'm fed
> up with it.

Yeah, I once used perf_event_open() to parse the trace events, I
understand how painful it is. Fortunately tools like bcc mostly hides
the ABI from end user. To be fair, kprobe has the same problem if not
worse, different compilers could inline different kernel functions, not
to mention kernel functions could change at any time.

OTOH, the tracepoint text interface is sufficient to help people to inspect
kernel internals, like in this case I can observe when a cpu cgroup is
throttled or unthrottled. Of course they are not friendly for programming.


      reply	other threads:[~2018-05-24 22:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22  6:20 [PATCH 0/3] sched/fair: improve CFS throttle Cong Wang
2018-05-22  6:20 ` [PATCH 1/3] sched/fair: make CFS bandwidth slice per cpu group Cong Wang
2018-05-22  6:20 ` [PATCH 2/3] sched/fair: accumulate unused cpu time for CFS throttle Cong Wang
2018-05-22  6:20 ` [PATCH 3/3] sched/fair: add tracepoints for cfs throttle Cong Wang
     [not found]   ` <>
2018-05-23  0:34     ` Cong Wang
2018-05-23  9:09     ` Peter Zijlstra
2018-05-24  4:40       ` Cong Wang
2018-05-24  7:11         ` Peter Zijlstra
2018-05-24 22:23           ` Cong Wang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH 3/3] sched/fair: add tracepoints for cfs throttle' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).