From: Tao Chen <chen.dylane@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Quentin Monnet <qmo@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
bpf <bpf@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next 3/3] bpftool: Display cookie for raw_tp link probe
Date: Fri, 30 May 2025 01:50:48 +0800 [thread overview]
Message-ID: <ffd23260-f214-482c-aef0-3fb49dbfa1d0@linux.dev> (raw)
In-Reply-To: <CAADnVQJVFffjzgZ0o_gAGJHwHHXn+UjawhAwknaTfgdQpjY3xA@mail.gmail.com>
在 2025/5/30 01:11, Alexei Starovoitov 写道:
> On Thu, May 29, 2025 at 10:01 AM Tao Chen <chen.dylane@linux.dev> wrote:
>>
>> Display cookie for raw_tp link probe, in plain mode:
>>
>> #bpftool link
>>
>> 22: raw_tracepoint prog 14
>> tp 'sys_enter' cookie 23925373020405760
>> pids test_progs(176)
>
> Curious number.
> What 0x55000000000000 was used for ?
Yes, no practical in fact, i just ran the selftest case in bpf_cookie.c.
raw_tp_opts.cookie = cookie = 0x55000000000000L;
--
Best Regards
Tao Chen
next prev parent reply other threads:[~2025-05-29 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 16:57 [PATCH bpf-next 1/3] bpf: Add cookie to raw_tp bpf_link_info Tao Chen
2025-05-29 16:57 ` [PATCH bpf-next 2/3] selftests/bpf: Add cookies check for raw_tp fill_link_info test Tao Chen
2025-05-29 16:57 ` [PATCH bpf-next 3/3] bpftool: Display cookie for raw_tp link probe Tao Chen
2025-05-29 17:11 ` Alexei Starovoitov
2025-05-29 17:50 ` Tao Chen [this message]
2025-05-31 8:30 ` [PATCH bpf-next 1/3] bpf: Add cookie to raw_tp bpf_link_info Jiri Olsa
2025-06-01 6:57 ` Tao Chen
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=ffd23260-f214-482c-aef0-3fb49dbfa1d0@linux.dev \
--to=chen.dylane@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.