mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
	petr.pavlu@suse.com, samitolvanen@google.com,
	da.gomez@samsung.com, masahiroy@kernel.org, deller@gmx.de,
	linux-arch@vger.kernel.org, live-patching@vger.kernel.org,
	kris.van.hees@oracle.com
Subject: Re: [PATCH v3] selftests: add new kallsyms selftests
Date: Thu, 28 Nov 2024 11:34:06 -0800	[thread overview]
Message-ID: <Z0jFruPWqtieVLtH@bombadil.infradead.org> (raw)
In-Reply-To: <CAMuHMdVG3Z63BruhrnQtSadCnaKZ+hpwFDJDnitXST8fRNYoLQ@mail.gmail.com>

On Thu, Nov 28, 2024 at 03:10:34PM +0100, Geert Uytterhoeven wrote:
> Despite the warning, I gave this a try on m68k (cross-compiled on i7 ;-).
> However, I didn't notice any extra-ordinary build times.

I had some large values before this got merged and due to this
slowing down builds 2x I reduced the defaults. The current defaults
are no known as TEST_KALLSYMS_LARGE.

> Also, when running the test manually on ARAnyM, everything runs
> in the blink of an eye.  I didn't use the script, but ran all commands
> manually.  I tried insmodding a/b/c/d, c/a/b, a/c/d/b.
> 
> Is this expected?

I tried to clarify the ranges known we can use to mess with this test
a bit more in the recent fixes on modules-next [0] so since you want
to see some things blow up try TEST_KALLSYMS_MAX, on some systems this
is reported to crash the build.

It is why I had reduced the original values a bit...

[0] git://git.kernel.org/pub/scm/linux/kernel/git/modules/linux.git modules-next

  Luis


      reply	other threads:[~2024-11-28 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 19:33 Luis Chamberlain
2024-10-23 17:28 ` Jeff Johnson
2024-10-24 20:21   ` Luis Chamberlain
2024-10-29 16:24 ` Sami Tolvanen
2024-11-06  0:21   ` Luis Chamberlain
2024-11-28 14:10 ` Geert Uytterhoeven
2024-11-28 19:34   ` Luis Chamberlain [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=Z0jFruPWqtieVLtH@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=da.gomez@samsung.com \
    --cc=deller@gmx.de \
    --cc=geert@linux-m68k.org \
    --cc=kris.van.hees@oracle.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=samitolvanen@google.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

all inboxes | Powered by JetHome®