linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	linux-modules@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,
	Masahiro Yamada <masahiroy@kernel.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Jiri Olsa <olsajiri@gmail.com>,
	Elena Zannoni <elena.zannoni@oracle.com>
Subject: Re: [PATCH v5 1/4] kbuild: add mod(name,file)_flags to assembler flags for module objects
Date: Wed, 14 Aug 2024 15:42:19 -0400	[thread overview]
Message-ID: <Zr0Im8k6KSqfZLyp@oracle.com> (raw)
In-Reply-To: <20240814131746.0a226e34@gandalf.local.home>

On Wed, Aug 14, 2024 at 01:17:46PM -0400, Steven Rostedt wrote:
> On Mon, 15 Jul 2024 23:10:42 -0400
> Kris Van Hees <kris.van.hees@oracle.com> wrote:
> 
> 
> As mentioned before, should start off with the goal.
> 
>   In order to create the file at build time, modules.builtin.ranges, that
>   contains the range of addresses for all built-in modules, there needs to
>   be a way to identify what code is compiled into modules.
> 
>   To identify what code is compiled into modules during a kernel build, ...

Ok, I see what you mean.  Fixing that.  Thanks!

 > In order to be able to identify what code is compiled into modules (even
> > built-in modules) during a kernel build, one can look for the presence
> > of the -DKBUILD_MODFILE and -DKBUILD_MODNAME options in the compile
> > command lines.  A simple grep in .*.cmd files for those options is
> > sufficient for this.
> > 
> > Unfortunately, these options are only passed when compiling C source files.
> > Various modules also include objects built from assembler source, and these
> > options are not passed in that case.
> > 
> > Adding $(modfile_flags) to modkern_aflags (similar to modkern_cflahs), and
> > adding $(modname_flags) to a_flags (similar to c_flags) makes it possible
> > to identify which objects are compiled into modules for both C and
> > assembler soure files.
> 
> The rest looks good.
> 
> Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>

Thanks!

> 
> -- Steve
> 
> > 
> > Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
> > ---
> >  scripts/Makefile.lib | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
> > index 9f06f6aaf7fc..f4aec3553ff2 100644
> > --- a/scripts/Makefile.lib
> > +++ b/scripts/Makefile.lib
> > @@ -238,7 +238,7 @@ modkern_rustflags =                                              \
> >  
> >  modkern_aflags = $(if $(part-of-module),				\
> >  			$(KBUILD_AFLAGS_MODULE) $(AFLAGS_MODULE),	\
> > -			$(KBUILD_AFLAGS_KERNEL) $(AFLAGS_KERNEL))
> > +			$(KBUILD_AFLAGS_KERNEL) $(AFLAGS_KERNEL) $(modfile_flags))
> >  
> >  c_flags        = -Wp,-MMD,$(depfile) $(NOSTDINC_FLAGS) $(LINUXINCLUDE)     \
> >  		 -include $(srctree)/include/linux/compiler_types.h       \
> > @@ -248,7 +248,7 @@ c_flags        = -Wp,-MMD,$(depfile) $(NOSTDINC_FLAGS) $(LINUXINCLUDE)     \
> >  rust_flags     = $(_rust_flags) $(modkern_rustflags) @$(objtree)/include/generated/rustc_cfg
> >  
> >  a_flags        = -Wp,-MMD,$(depfile) $(NOSTDINC_FLAGS) $(LINUXINCLUDE)     \
> > -		 $(_a_flags) $(modkern_aflags)
> > +		 $(_a_flags) $(modkern_aflags) $(modname_flags)
> >  
> >  cpp_flags      = -Wp,-MMD,$(depfile) $(NOSTDINC_FLAGS) $(LINUXINCLUDE)     \
> >  		 $(_cpp_flags)

  reply	other threads:[~2024-08-14 19:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16  3:10 [PATCH v5 0/4] Generate address range data for built-in modules Kris Van Hees
2024-07-16  3:10 ` [PATCH v5 1/4] kbuild: add mod(name,file)_flags to assembler flags for module objects Kris Van Hees
2024-08-14 17:17   ` Steven Rostedt
2024-08-14 19:42     ` Kris Van Hees [this message]
2024-07-16  3:10 ` [PATCH v5 2/4] kbuild, kconfig: generate offset range data for builtin modules Kris Van Hees
2024-08-14 19:04   ` Steven Rostedt
2024-08-14 19:52     ` Kris Van Hees
2024-07-16  3:10 ` [PATCH v5 3/4] scripts: add verifier script for builtin module range data Kris Van Hees
2024-08-14 19:19   ` Steven Rostedt
2024-08-14 19:59     ` Kris Van Hees
2024-08-14 20:16       ` Steven Rostedt
2024-08-15  1:02         ` Kris Van Hees
2024-07-16  3:10 ` [PATCH v5 4/4] module: add install target for modules.builtin.ranges Kris Van Hees
2024-08-14 16:45 ` [PATCH v5 0/4] Generate address range data for built-in modules Steven Rostedt

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=Zr0Im8k6KSqfZLyp@oracle.com \
    --to=kris.van.hees@oracle.com \
    --cc=elena.zannoni@oracle.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=olsajiri@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;
as well as URLs for NNTP newsgroup(s).