linux-kernel - Question about 'for_each_kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJNi4rM0K=-wgJrS0iLMkam77JTO7oRxcP9VkHGbuTiVGBovMA@mail.gmail.com>
Date:   Thu, 20 Oct 2022 17:32:57 +0800
From:   richard clark <richard.xnu.clark@...il.com>
To:     rostedt@...dmis.org, bristot@...nel.org
Cc:     linux-trace-devel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Question about 'for_each_kernel_tracepoint(...)' function

Hi,
Can this function only find the trace points defined in the kernel
image? I want to define a trace event in my kernel module A, then B
module to register a probe callback function for that event TP in A. I
want to kick off a timer in A and call the traced function
periodically, thus I can monitor the events happening in A from B.

Can I do that, is it possible?

Richard