From: Song Liu <songliubraving@fb.com>
To: Yonghong Song <yhs@fb.com>
Cc: bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Alexei Starovoitov" <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"Kernel Team" <Kernel-team@fb.com>,
john fastabend <john.fastabend@gmail.com>,
"kpsingh@chromium.org" <kpsingh@chromium.org>
Subject: Re: [PATCH v2 bpf-next 2/4] bpf: introduce helper bpf_get_task_stak()
Date: Fri, 26 Jun 2020 22:37:38 +0000 [thread overview]
Message-ID: <81642975-984F-4C87-8847-D7BF51CADB03@fb.com> (raw)
In-Reply-To: <572bd252-2748-d776-0e7b-eca5302dba76@fb.com>
> On Jun 26, 2020, at 8:40 AM, Yonghong Song <yhs@fb.com> wrote:
>
>
>
> On 6/25/20 5:13 PM, Song Liu wrote:
>> Introduce helper bpf_get_task_stack(), which dumps stack trace of given
>> task. This is different to bpf_get_stack(), which gets stack track of
>> current task. One potential use case of bpf_get_task_stack() is to call
>> it from bpf_iter__task and dump all /proc/<pid>/stack to a seq_file.
>> bpf_get_task_stack() uses stack_trace_save_tsk() instead of
>> get_perf_callchain() for kernel stack. The benefit of this choice is that
>> stack_trace_save_tsk() doesn't require changes in arch/. The downside of
>> using stack_trace_save_tsk() is that stack_trace_save_tsk() dumps the
>> stack trace to unsigned long array. For 32-bit systems, we need to
>> translate it to u64 array.
>> Signed-off-by: Song Liu <songliubraving@fb.com>
>>
[...]
>> +++ b/include/uapi/linux/bpf.h
>> @@ -3252,6 +3252,38 @@ union bpf_attr {
>> * case of **BPF_CSUM_LEVEL_QUERY**, the current skb->csum_level
>> * is returned or the error code -EACCES in case the skb is not
>> * subject to CHECKSUM_UNNECESSARY.
>> + *
>> + * int bpf_get_task_stack(struct task_struct *task, void *buf, u32 size, u64 flags)
>
> Andrii's recent patch changed the return type to 'long' to align with
> kernel u64 return type for better llvm code generation.
>
> Please rebase and you will see the new convention.
Will fix.
>
>> + * Description
>>
[...]
>> +static struct perf_callchain_entry *
>> +get_callchain_entry_for_task(struct task_struct *task, u32 init_nr)
>> +{
>> + struct perf_callchain_entry *entry;
>> + int rctx;
>> +
>> + entry = get_callchain_entry(&rctx);
>> +
>> + if (rctx == -1)
>> + return NULL;
>
> Is this needed? Should be below !entry enough?
It is needed before Peter's suggestion. After applying Peter's patch,
this is no longer needed.
Thanks,
Song
next prev parent reply other threads:[~2020-06-26 22:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 0:13 [PATCH v2 bpf-next 0/4] bpf: introduce bpf_get_task_stack() Song Liu
2020-06-26 0:13 ` [PATCH v2 bpf-next 1/4] perf: export get/put_chain_entry() Song Liu
2020-06-26 11:00 ` Peter Zijlstra
2020-06-26 20:06 ` Andrii Nakryiko
2020-06-26 21:38 ` Song Liu
2020-06-26 21:29 ` Song Liu
2020-06-26 0:13 ` [PATCH v2 bpf-next 2/4] bpf: introduce helper bpf_get_task_stak() Song Liu
2020-06-26 15:40 ` Yonghong Song
2020-06-26 22:37 ` Song Liu [this message]
2020-06-26 20:17 ` Andrii Nakryiko
2020-06-26 20:22 ` Andrii Nakryiko
2020-06-26 22:45 ` Song Liu
2020-06-26 22:51 ` Andrii Nakryiko
2020-06-26 23:47 ` Song Liu
2020-06-27 0:06 ` Andrii Nakryiko
2020-06-26 0:13 ` [PATCH v2 bpf-next 3/4] bpf: allow %pB in bpf_seq_printf() and bpf_trace_printk() Song Liu
2020-06-26 15:44 ` [Potential Spoof] " Yonghong Song
2020-06-26 0:13 ` [PATCH v2 bpf-next 4/4] selftests/bpf: add bpf_iter test with bpf_get_task_stack() Song Liu
2020-06-26 15:52 ` Yonghong Song
2020-06-26 20:21 ` Andrii Nakryiko
2020-06-26 23:05 ` Song Liu
2020-06-26 23:11 ` Andrii Nakryiko
2020-06-26 23:40 ` Song Liu
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=81642975-984F-4C87-8847-D7BF51CADB03@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--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).