Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 20 Oct 2022 22:12:55 -0400
From:   Steven Rostedt <rostedt@goodmis.org>
To:     richard clark <richard.xnu.clark@gmail.com>
Cc:     bristot@kernel.org, linux-trace-devel@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: Question about 'for_each_kernel_tracepoint(...)' function
Message-ID: <20221020221255.5b3dffe1@gandalf.local.home>
In-Reply-To: <CAJNi4rMVUzfZJPge=ncaULD87wLQ4TwWS=oKDuC1hZMoWi0OjA@mail.gmail.com>
References: <CAJNi4rM0K=-wgJrS0iLMkam77JTO7oRxcP9VkHGbuTiVGBovMA@mail.gmail.com>
        <20221020111439.76e72230@gandalf.local.home>
        <CAJNi4rMVUzfZJPge=ncaULD87wLQ4TwWS=oKDuC1hZMoWi0OjA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 21 Oct 2022 09:43:14 +0800
richard clark <richard.xnu.clark@gmail.com> wrote:


> Ah, as you can see that I did it, but the result is not what I
> expected :-). Help?

Looking at the code, I see it does indeed only look at builtin tracepoints.

But if you want one module to have access to the tracepoints of another,
then you can have the first one export it.

EXPORT_SYMBOL_TRACEPOINT_GPL(function_event_a);

And then module b should have access to it.

-- Steve