From: Peter Zijlstra <peterz@infradead.org>
To: Teng Qin <qinteng@fb.com>
Cc: Alexei Starovoitov <ast@fb.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"bgregg@netflix.com" <bgregg@netflix.com>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
Yonghong Song <yhs@fb.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH tip 0/3] Improvements of scheduler related Tracepoints
Date: Fri, 15 Dec 2017 10:53:05 +0100 [thread overview]
Message-ID: <20171215095305.o7yinfsoym6bgaem@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <935FB65D-395D-4122-8E40-75CA04FF2111@fb.com>
On Fri, Dec 15, 2017 at 08:53:30AM +0000, Teng Qin wrote:
> To have access to related task_struct is one of the main purposes of these
> patches. Take sched_switch as an example. We depend on the implementation
> of the Tracepoint is called from prev or next (which could, although unlikedly,
> change) and use current to get that task_struct, which feels, correct
> me if I'm wrong, kind of defeating the purpose of Tracepoints being more
> implementation-independent than kprobes. Then we have to figure out another
> Tracepoint or most likely a kprobe function to get the other (prev or next)
> task_struct.
Go read how tracepoints work. The tracepoint_probe things get you
exactly what you want.
next prev parent reply other threads:[~2017-12-15 9:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 20:20 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 ` [PATCH tip 0/3] Improvements of scheduler related Tracepoints Peter Zijlstra
2017-12-15 3:16 ` Alexei Starovoitov
2017-12-15 7:39 ` Peter Zijlstra
2017-12-15 8:53 ` Teng Qin
2017-12-15 9:53 ` Peter Zijlstra [this message]
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=20171215095305.o7yinfsoym6bgaem@hirez.programming.kicks-ass.net \
--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
Powered by JetHome