All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: objtool hang/loop?
Date: Wed, 4 Aug 2021 13:47:30 -0700	[thread overview]
Message-ID: <f45ba1d7-a175-c284-5489-b2c2eaa7131c@infradead.org> (raw)
In-Reply-To: <20210804183419.k7p3tvqerwgzxpuz@treble>

On 8/4/21 11:34 AM, Josh Poimboeuf wrote:
> On Wed, Jul 28, 2021 at 07:25:21PM -0700, Randy Dunlap wrote:
>> Hi Josh & Peter,
>>
>> Yesterday (2021-07-27), one of my x86_64 randconfig build ran for
>> over 2 hours (it's a slow core i5 laptop and spinning rust media).
>> I killed it and reran the .config file today on linux-next-20210728.
>> I killed this one after 30 minutes on its last message:
>>    OBJTOOL vmlinux.o
>>
>> This is a .config with # CONFIG_MODULES is not set.
>> vmlinux.o is 253 MB in size.
>> I see that using verbose make (V=1) won't help me any here.
>>
>> The problematic (if it is a problem: maybe I didn't wait long
>> enough?) .config file is attached.  The gzipped vmlinux.o file is at:
>>    http://www.infradead.org/~rdunlap/vmlinux.o.gz
>>
>> If there is a problem, I can test any patches...
> 
> Hi Randy,
> 
> I'm guessing your laptop doesn't have a lot of RAM.  I ran

Hey, it has a whopping 6 GB of RAM. :)

>    /usr/bin/time -v tools/objtool/objtool check --noinstr --vmlinux --no-fp --uaccess vmlinux.o
> 
> It showed a max RSS of 6.5GB.
> 
> Can you try this patch from Peter?  It halves the memory usage.
> 
>    https://lkml.kernel.org/r/20210507164925.GC54801@worktop.programming.kicks-ass.net

Yes, that fixes the problem for me. Thanks.

Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>

-- 
~Randy



  reply	other threads:[~2021-08-04 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  2:25 linux-next: objtool hang/loop? Randy Dunlap
2021-08-04 18:34 ` Josh Poimboeuf
2021-08-04 20:47   ` Randy Dunlap [this message]
2021-08-05 11:05   ` Peter Zijlstra

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=f45ba1d7-a175-c284-5489-b2c2eaa7131c@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.