public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jessica Yu <jeyu@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Christoph Hellwig" <hch@lst.de>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Miroslav Benes" <mbenes@suse.cz>,
	"Emil Velikov" <emil.l.velikov@gmail.com>,
	"Masahiro Yamada" <masahiroy@kernel.org>
Subject: Re: [GIT PULL] Modules updates for v5.12
Date: Wed, 24 Feb 2021 09:33:28 +0100	[thread overview]
Message-ID: <YDYPWAtoDpyD9D4Z@gunter> (raw)
In-Reply-To: <CAHk-=wj27tmZBzFRTZTAEPd6eRBzP5xCkQM+1cuSx7vzv8K4=g@mail.gmail.com>

+++ Linus Torvalds [23/02/21 12:03 -0800]:
>On Tue, Feb 23, 2021 at 12:01 PM Christoph Hellwig <hch@lst.de> wrote:
>>
>> Does your build now enable TRIM_UNUSED_KSYMS but previously didn't by
>> chance?
>
>Crossed emails.
>
>This is plain "make allmodconfig", so yes, now it will enable TRIM_UNUSED_KSYMS.
>
>This is unacceptably slow. If that symbol trimming takes 30% of the
>whole kernel build time, it needs to be fixed or removed.

[ Adding Masahiro to CC ]

It looks like CONFIG_TRIM_UNUSED_KSYMS had been hiding behind
CONFIG_UNUSED_SYMBOLS all this time, and once the EXPORT_UNUSED_SYMBOL
stuff was removed, it exposed that option to be selected by
allyesconfig. That option had previously caused build issues on
powerpc on linux-next, so I had temporarily marked that as BROKEN on
powerpc until Masahiro's fix landed in linux-next. I was not aware of
the additional build slowdown issue :/ In any case, Christoph's
suggestion to invert the option sounds reasonable, since the mips
defconfig selects it, it does not seem totally unused.

  parent reply	other threads:[~2021-02-24  8:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 15:42 [GIT PULL] Modules updates for v5.12 Jessica Yu
2021-02-23 18:26 ` Linus Torvalds
2021-02-23 18:42   ` Linus Torvalds
2021-02-23 19:55     ` Linus Torvalds
2021-02-23 20:01       ` Christoph Hellwig
2021-02-23 20:03         ` Linus Torvalds
2021-02-23 20:07           ` Linus Torvalds
2021-02-24  7:52             ` Christoph Hellwig
2021-02-24 14:13               ` Jessica Yu
2021-02-24 14:46                 ` Masahiro Yamada
2021-02-24 15:30                   ` Masahiro Yamada
2021-02-24 16:56                   ` Linus Torvalds
2021-02-24  8:33           ` Jessica Yu [this message]
2021-02-24 14:40             ` Masahiro Yamada
2021-02-24 19:36               ` Rasmus Villemoes
2021-02-25 15:49                 ` Masahiro Yamada
2021-02-25 16:17                   ` Masahiro Yamada
2021-02-25 16:19                   ` Rasmus Villemoes
2021-02-25 18:37                     ` Masahiro Yamada
2021-02-23 20:01       ` Linus Torvalds
2021-02-23 20:32 ` pr-tracker-bot

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=YDYPWAtoDpyD9D4Z@gunter \
    --to=jeyu@kernel.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mbenes@suse.cz \
    --cc=torvalds@linux-foundation.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