Linux Modules
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: samitolvanen@google.com, petr.pavlu@suse.com,
	da.gomez@samsung.com, linux-modules@vger.kernel.org,
	patches@lists.linux.dev, linux-kernel@vger.kernel.org,
	masahiroy@kernel.org, mmaurer@google.com, arnd@arndb.de,
	deller@gmx.de, song@kernel.org
Subject: Re: [GIT PULL] Modules changes for v6.13-rc1
Date: Wed, 27 Nov 2024 14:35:36 -0800	[thread overview]
Message-ID: <Z0eeuCyUGcKgsc5h@bombadil.infradead.org> (raw)
In-Reply-To: <CAHk-=wjCkJsdLageTx6C4n--aYFoO6gSRe0Rwcbk1jQdOdiPfg@mail.gmail.com>

On Wed, Nov 27, 2024 at 01:22:37PM -0800, Linus Torvalds wrote:
> On Tue, 26 Nov 2024 at 17:10, Luis Chamberlain <mcgrof@kernel.org> wrote:
> >
> > Highlights for this merge window:
> 
> Lowlights:
> 
> >   * Adds a new modules selftests: kallsyms which helps us tests find_symbol()
> >     and the limits of kallsyms on Linux today.
> 
> This is completely broken.
> 
> Try doing "make allmodconfig" and then do "make" twice in a row.
> 
> It re-generates the tests, so you see this:
> 
>   GEN     lib/tests/module/test_kallsyms_a.c
>   GEN     lib/tests/module/test_kallsyms_b.c
>   GEN     lib/tests/module/test_kallsyms_c.c
>   GEN     lib/tests/module/test_kallsyms_d.c
>   CC [M]  lib/tests/module/test_kallsyms_a.o
>   CC [M]  lib/tests/module/test_kallsyms_b.o
>   CC [M]  lib/tests/module/test_kallsyms_c.o
>   CC [M]  lib/tests/module/test_kallsyms_d.o
>   LD [M]  lib/tests/module/test_kallsyms_a.ko
>   LD [M]  lib/tests/module/test_kallsyms_b.ko
>   LD [M]  lib/tests/module/test_kallsyms_c.ko
>   LD [M]  lib/tests/module/test_kallsyms_d.ko
> 
> both times, and this has made the empty build slow down by about a
> factor of two.
> 
> Which is a big deal, because the "empty build" is actually fairly
> important for me. It's the baseline build test performance, and with
> small pulls it actually dominates.
> 
> So this isn't ok. Please fix asap, because otherwise I will just
> revert it - it really does affect my workflow that much.

Sorry about that, I'm on it.

  Luis

  reply	other threads:[~2024-11-27 22:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27  1:10 [GIT PULL] Modules changes for v6.13-rc1 Luis Chamberlain
2024-11-27 18:33 ` pr-tracker-bot
2024-11-27 21:22 ` Linus Torvalds
2024-11-27 22:35   ` Luis Chamberlain [this message]
2024-11-27 23:26     ` Luis Chamberlain
2024-11-27 23:56       ` Linus Torvalds
2024-11-28  2:09         ` Masahiro Yamada
2024-11-28  2:38           ` Luis Chamberlain
2024-11-28  2:48             ` Masahiro Yamada
2024-11-28  2:22         ` Luis Chamberlain
2024-11-28  2:42           ` Luis Chamberlain
2024-11-28  2:56             ` Masahiro Yamada
2024-11-28  3:02               ` Luis Chamberlain
2024-11-28  3:10                 ` Luis Chamberlain
2024-11-28  3:14                   ` Masahiro Yamada
2024-11-28  3:12                 ` Masahiro Yamada
2024-11-28  2:44           ` Masahiro Yamada

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=Z0eeuCyUGcKgsc5h@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=arnd@arndb.de \
    --cc=da.gomez@samsung.com \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mmaurer@google.com \
    --cc=patches@lists.linux.dev \
    --cc=petr.pavlu@suse.com \
    --cc=samitolvanen@google.com \
    --cc=song@kernel.org \
    --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