linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Petr Pavlu <petr.pavlu@suse.com>, Arnd Bergmann <arnd@arndb.de>,
	linux-arch@vger.kernel.org,  linux-modules@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] codetag: Avoid unused alloc_tags sections/symbols
Date: Thu, 13 Mar 2025 11:07:53 -0700	[thread overview]
Message-ID: <CAJuCfpEpFqLX-WtXzSdktkp7w3s3JWeSqeG_fms6Ydun+docTA@mail.gmail.com> (raw)
In-Reply-To: <jmcazyqlkimqhswwqn2du7ik5sbm5fommonrgovy5d6knqbqcr@xebmu4akkkoy>

On Thu, Mar 13, 2025 at 10:16 AM Kent Overstreet
<kent.overstreet@linux.dev> wrote:
>
> On Thu, Mar 13, 2025 at 03:29:20PM +0100, Petr Pavlu wrote:
> > With CONFIG_MEM_ALLOC_PROFILING=n, vmlinux and all modules unnecessarily
> > contain the symbols __start_alloc_tags and __stop_alloc_tags, which define
> > an empty range. In the case of modules, the presence of these symbols also
> > forces the linker to create an empty .codetag.alloc_tags section.
> >
> > Update codetag.lds.h to make the data conditional on
> > CONFIG_MEM_ALLOC_PROFILING.
> >
> > Signed-off-by: Petr Pavlu <petr.pavlu@suse.com>
>
> Reviewed-by: Kent Overstreet <kent.overstreet@linux.dev>

Reviewed-by: Suren Baghdasaryan <surenb@google.com>

>
> > ---
> >  include/asm-generic/codetag.lds.h | 10 ++++++++--
> >  1 file changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/include/asm-generic/codetag.lds.h b/include/asm-generic/codetag.lds.h
> > index 372c320c5043..0ea1fa678405 100644
> > --- a/include/asm-generic/codetag.lds.h
> > +++ b/include/asm-generic/codetag.lds.h
> > @@ -2,6 +2,12 @@
> >  #ifndef __ASM_GENERIC_CODETAG_LDS_H
> >  #define __ASM_GENERIC_CODETAG_LDS_H
> >
> > +#ifdef CONFIG_MEM_ALLOC_PROFILING
> > +#define IF_MEM_ALLOC_PROFILING(...) __VA_ARGS__
> > +#else
> > +#define IF_MEM_ALLOC_PROFILING(...)
> > +#endif
> > +
> >  #define SECTION_WITH_BOUNDARIES(_name)       \
> >       . = ALIGN(8);                   \
> >       __start_##_name = .;            \
> > @@ -9,7 +15,7 @@
> >       __stop_##_name = .;
> >
> >  #define CODETAG_SECTIONS()           \
> > -     SECTION_WITH_BOUNDARIES(alloc_tags)
> > +     IF_MEM_ALLOC_PROFILING(SECTION_WITH_BOUNDARIES(alloc_tags))
> >
> >  /*
> >   * Module codetags which aren't used after module unload, therefore have the
> > @@ -28,6 +34,6 @@
> >   * unload them individually once unused.
> >   */
> >  #define MOD_SEPARATE_CODETAG_SECTIONS()              \
> > -     MOD_SEPARATE_CODETAG_SECTION(alloc_tags)
> > +     IF_MEM_ALLOC_PROFILING(MOD_SEPARATE_CODETAG_SECTION(alloc_tags))
> >
> >  #endif /* __ASM_GENERIC_CODETAG_LDS_H */
> >
> > base-commit: 80e54e84911a923c40d7bee33a34c1b4be148d7a
> > --
> > 2.43.0
> >

      reply	other threads:[~2025-03-13 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 14:29 [PATCH] codetag: Avoid unused alloc_tags sections/symbols Petr Pavlu
2025-03-13 17:16 ` Kent Overstreet
2025-03-13 18:07   ` Suren Baghdasaryan [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=CAJuCfpEpFqLX-WtXzSdktkp7w3s3JWeSqeG_fms6Ydun+docTA@mail.gmail.com \
    --to=surenb@google.com \
    --cc=arnd@arndb.de \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=petr.pavlu@suse.com \
    /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).