From: Hari Bathini <hbathini@linux.ibm.com>
To: "Nassiri, Mohammad" <mnassiri@ciena.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Cc: "linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>,
"michael@ellerman.id.au" <michael@ellerman.id.au>,
"masami.hiramatsu@linaro.org" <masami.hiramatsu@linaro.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Nicholas Piggin <npiggin@gmail.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>
Subject: Re: [**EXTERNAL**] Re: [PPC][Tracing] Missing syscalls:* ftrace/perf events on PowerPC vs x86
Date: Fri, 20 Feb 2026 13:24:08 +0530 [thread overview]
Message-ID: <38e1160d-26ea-4432-9ca4-1c606dd187ac@linux.ibm.com> (raw)
In-Reply-To: <CH2PR04MB682162D39BB7E7EB0F0695AFC56AA@CH2PR04MB6821.namprd04.prod.outlook.com>
On 18/02/26 7:26 pm, Nassiri, Mohammad wrote:
>> You should see syscall enter/exit tracepoints on v5.10.x without syscall
>> wrapper patchset referred above. Are you using v5.10.250 ?
>> Also, would help, if you can share the .config you used.
> Hi Hari,
Hi Mohammad,
>
> No, I'm not using the latest v5.10.250. I tested on two versions --- v5.10.174 and v5.10.239 --- and I still see the issue on both.
> For your reference, here is a grep from my .config showing most of the tracing options I enabled while troubleshooting this issue.
OK. Tried v5.10.250 as well as v5.10.174 with the similar config
options. Could see syscall enter/exit tracepoints..
- Hari
prev parent reply other threads:[~2026-02-20 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 20:10 [PPC][Tracing] Missing syscalls:* ftrace/perf events on PowerPC vs x86 Nassiri, Mohammad
2026-02-17 20:23 ` Steven Rostedt
2026-02-17 20:47 ` [**EXTERNAL**] " Nassiri, Mohammad
2026-02-18 5:33 ` Hari Bathini
2026-02-18 13:56 ` [**EXTERNAL**] " Nassiri, Mohammad
2026-02-20 7:54 ` Hari Bathini [this message]
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=38e1160d-26ea-4432-9ca4-1c606dd187ac@linux.ibm.com \
--to=hbathini@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-trace-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masami.hiramatsu@linaro.org \
--cc=michael@ellerman.id.au \
--cc=mnassiri@ciena.com \
--cc=npiggin@gmail.com \
--cc=rostedt@goodmis.org \
/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