From: Yauheni Kaliuta <ykaliuta@redhat.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Yonghong Song <yhs@fb.com>, bpf <bpf@vger.kernel.org>,
Artem Savkov <asavkov@redhat.com>,
Viktor Malik <vmalik@redhat.com>,
jmarchan@redhat.com
Subject: Re: sys_enter tracepoint ctx structure
Date: Thu, 20 Apr 2023 23:37:41 +0300 [thread overview]
Message-ID: <xunyjzy6z3vu.fsf@redhat.com> (raw)
In-Reply-To: <CAADnVQ+JdPGV95Y30PskgdOomU2K0UXsoCydgqaJfJ5j4S8BtQ@mail.gmail.com> (Alexei Starovoitov's message of "Thu, 20 Apr 2023 08:59:09 -0700")
Hi, Alexei!
>>>>> On Thu, 20 Apr 2023 08:59:09 -0700, Alexei Starovoitov wrote:
> On Thu, Apr 20, 2023 at 6:57 AM Yauheni Kaliuta <ykaliuta@redhat.com> wrote:
>> Hi!
>>
>> Should perf_call_bpf_enter/exit (kernel/trace/trace_syscalls.c)
>> use struct trace_event_raw_sys_enter/exit instead of locally
>> crafted struct syscall_tp_t nowadays?
> No. It needs syscall_tp_t.
> test_progs's vmlinux test
>> expects it as the context.
>>
> what do you mean? Pls share a code pointer?
https://github.com/torvalds/linux/blob/master/tools/testing/selftests/bpf/progs/test_vmlinux.c#L19
SEC("tp/syscalls/sys_enter_nanosleep")
int handle__tp(struct trace_event_raw_sys_enter *args)
So, should it use different structure then? syscall_tp_t to be
declared publicly?
>>
>> Or at least use struct trace_entry instead of struct pt_regs?
>>
> no. It needs a pointer to pt_regs.
> See all of the pe_* flavor of helpers.
>>
>> I have a problem with one RT patch with extends trace_entry.
>>
> Just extend it. It shouldn't matter.
> I'm likely missing something.
Or me. Let's figure out :)
--
WBR,
Yauheni Kaliuta
next prev parent reply other threads:[~2023-04-20 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 13:50 sys_enter tracepoint ctx structure Yauheni Kaliuta
[not found] ` <CAADnVQ+JdPGV95Y30PskgdOomU2K0UXsoCydgqaJfJ5j4S8BtQ@mail.gmail.com>
2023-04-20 16:02 ` Fwd: " Alexei Starovoitov
2023-04-20 20:37 ` Yauheni Kaliuta [this message]
2023-04-20 20:54 ` Alexei Starovoitov
2023-04-20 21:40 ` Yauheni Kaliuta
2023-04-20 23:12 ` Alexei Starovoitov
2023-04-21 11:17 ` Yauheni Kaliuta
2023-04-21 16:02 ` Alexei Starovoitov
2023-04-23 9:04 ` Yauheni Kaliuta
2023-04-23 16:15 ` 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=xunyjzy6z3vu.fsf@redhat.com \
--to=ykaliuta@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=asavkov@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=jmarchan@redhat.com \
--cc=vmalik@redhat.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