From: Peter Zijlstra <peterz@infradead.org>
To: Teng Qin <qinteng@fb.com>
Cc: mingo@redhat.com, ast@fb.com, bgregg@netflix.com,
daniel@iogearbox.net, yhs@fb.com, linux-kernel@vger.kernel.org,
Kernel-team@fb.com
Subject: Re: [PATCH tip 0/3] Improvements of scheduler related Tracepoints
Date: Thu, 14 Dec 2017 21:49:32 +0100 [thread overview]
Message-ID: <20171214204932.GH3326@worktop> (raw)
In-Reply-To: <20171214202044.1629279-1-qinteng@fb.com>
On Thu, Dec 14, 2017 at 12:20:41PM -0800, Teng Qin wrote:
> This set of commits attempts to improve three scheduler related
> Tracepoints: sched_switch, sched_process_fork, sched_process_exit.
>
> Firstly, these commit add additional flag values, namely preempt,
> clone_flags and group_dead to these Tracepoints, to make information
> exposed via the Tracepoints more useful and complete.
>
> Secondly, these commits exposes task_struct pointers in these
> Tracepoints. The task_struct pointers are arguments of the Tracepoints
> and currently only used to compute struct field values. But for BPF
> programs attached to these Tracepoints, we may want to read additional
> task information via the task_struct pointers. This is currently either
> impossible, or we have to make assumption of whether the Tracepoint is
> running from previous / parent or next / child, and use current pointer
> instead. Exposing the task_struct pointers explicitly makes such use
> case easier and more reliable.
>
NAK
next prev parent reply other threads:[~2017-12-14 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 20:20 [PATCH tip 0/3] Improvements of scheduler related Tracepoints Teng Qin
2017-12-14 20:20 ` [PATCH tip 1/3] Improve sched_switch Tracepoint Teng Qin
2017-12-14 20:20 ` [PATCH tip 2/3] Improve sched_process_fork Tracepoint Teng Qin
2017-12-14 20:20 ` [PATCH tip 3/3] Improve sched_process_exit Tracepoint Teng Qin
2017-12-14 20:49 ` Peter Zijlstra [this message]
2017-12-15 3:16 ` [PATCH tip 0/3] Improvements of scheduler related Tracepoints Alexei Starovoitov
2017-12-15 7:39 ` Peter Zijlstra
2017-12-15 8:53 ` Teng Qin
2017-12-15 9:53 ` Peter Zijlstra
2017-12-15 17:09 ` Alexei Starovoitov
2017-12-18 9:11 ` Peter Zijlstra
2017-12-21 2:03 ` tracepoint_probe_register and bpf. Was: " Alexei Starovoitov
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171214204932.GH3326@worktop \
--to=peterz@infradead.org \
--cc=Kernel-team@fb.com \
--cc=ast@fb.com \
--cc=bgregg@netflix.com \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qinteng@fb.com \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).