From: Sam Ravnborg <sam@ravnborg.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Paulo Marques <pmarques@grupopie.com>
Subject: Re: [RFC PATCH] drop support for KALLSYMS_EXTRA_PASS
Date: Sat, 7 Jun 2008 12:51:46 +0200 [thread overview]
Message-ID: <20080607105146.GA25410@uranus.ravnborg.org> (raw)
In-Reply-To: <17789.1212657564@ocs10w>
On Thu, Jun 05, 2008 at 07:19:24PM +1000, Keith Owens wrote:
> Sam Ravnborg (on Tue, 3 Jun 2008 23:07:32 +0200) wrote:
> >We have not seen any reports on inconsistent kallsysms data recently
> >as in the last one or two years. At least I do not recall these
> >and google had no hits in my searching.
> >
> >So I suggest removing this as to simplify the final linking.
> >When doing "make allyesconfig" build this extra linking
> >takes considerably time (and I usually forgoet to turn it off).
> >
> >In addition this patch removes the debug target: debug_kallsyms
> >
> >diff --git a/Makefile b/Makefile
> >-define verify_kallsyms
> >- $(Q)$(if $($(quiet)cmd_sysmap), \
> >- echo ' $($(quiet)cmd_sysmap) .tmp_System.map' &&) \
> >- $(cmd_sysmap) .tmp_vmlinux$(last_kallsyms) .tmp_System.map
> >- $(Q)cmp -s System.map .tmp_System.map || \
> >- (echo Inconsistent kallsyms data; \
> >- echo Try setting CONFIG_KALLSYMS_EXTRA_PASS; \
> >- rm .tmp_kallsyms* ; /bin/false )
> >-endef
>
> I am not happy about removing the check for inconsistent kallsyms data.
> Changes to the tool chain could cause this problem to recur and we
> would not pick up on it. If we do keep the check for inconsistent data
> then we still need some way for the user to continue while the problem
> is investigated.
>
> Since your real complaint seems to be the extra time taken in make
> allyesconfig then the solution is easy. Change CONFIG_KALLSYMS_EXTRA_PASS
> to a Makefile option, KALLSYMS_EXTRA_PASS=y. No extra time required in
> make allyesconfig.
The primary complaint are the additional complexity in the Makefile.
See http://lkml.org/lkml/2008/6/4/436 for a much simpler
and thus more hackable method for linking vmlinux.
Sam
prev parent reply other threads:[~2008-06-07 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 21:07 [RFC PATCH] drop support for KALLSYMS_EXTRA_PASS Sam Ravnborg
2008-06-04 14:01 ` Paulo Marques
2008-06-05 9:19 ` Keith Owens
2008-06-07 10:51 ` Sam Ravnborg [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=20080607105146.GA25410@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kaos@ocs.com.au \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.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