All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: PATCH] tracing: Fix unused tracepoints when module uses only exported ones
Date: Tue, 9 Dec 2025 20:25:51 -0500	[thread overview]
Message-ID: <20251209202551.055c0f1b@fedora> (raw)
In-Reply-To: <3612840f-0c05-4797-8e75-872a306da45c@efficios.com>

On Mon, 8 Dec 2025 09:22:48 -0500
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:

> On 2025-12-08 08:53, Steven Rostedt wrote:
> > From: Steven Rostedt <rostedt@goodmis.org>  
> 
> Missing bracket for [PATCH] in subject.
> 
> > 
> > Building the KVM intel module failed to build with UT=1:  
> 
> failed -> fails (present ?)

After the patch is applied it will be in the past ;-)
> 
> > 
> > no __tracepoint_strings in file: arch/x86/kvm/kvm-intel.o
> > make[3]: *** [/work/git/test-linux.git/scripts/Makefile.modfinal:62: arch/x86/kvm/kvm-intel.ko] Error 1
> > 
> > The reason is that the module only uses the tracepoints defined and
> > exported by the main kvm module. The tracepoint-udpate.c code fails the  
> 
> I guess you mean "tracepoint-update.c" ?

Oops

> 
> > build if a tracepoint is used, but there's no tracepoints defined. But  
> 
> tracepoint

Actually, plural is fine here. Because it means one or more here.


> 
> > this is acceptable in modules if the tracepoints is defined in the vmlinux  
> 
> tracepoint

Actually, it should stay plural (as it is more than one), but needs s/is/are/

> 
> > proper or another module and exported.
> > 
> > Do not fail to build if a tracepoint is used but no tracepoints are  
> 
> tracepoint .. is
> 

Again, plural is OK here, but the other fixes can be done.

Although I see this right after I send a pull request to Linus, but
because I'm currently at the Maintainers Summit with Linus, and I don't
need to test this to fix it, I'll set up another pull request and tell
him to take the second one.

Thanks,

-- Steve


But, because it's just a change log fix and 

      reply	other threads:[~2025-12-10  1:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 13:53 PATCH] tracing: Fix unused tracepoints when module uses only exported ones Steven Rostedt
2025-12-08 14:22 ` Mathieu Desnoyers
2025-12-10  1:25   ` Steven Rostedt [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=20251209202551.055c0f1b@fedora \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.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 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.