From: Sam Ravnborg <sam@ravnborg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: rostedt@goodmis.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, zippel@linux-m68k.org,
mingo@elte.hu
Subject: Re: Better way to force a rebuild
Date: Wed, 10 Dec 2008 21:37:40 +0100 [thread overview]
Message-ID: <20081210203740.GA16674@uranus.ravnborg.org> (raw)
In-Reply-To: <20081210121048.6186eaf9.akpm@linux-foundation.org>
On Wed, Dec 10, 2008 at 12:10:48PM -0800, Andrew Morton wrote:
> On Wed, 10 Dec 2008 21:02:42 +0100
> Sam Ravnborg <sam@ravnborg.org> wrote:
>
> > On Wed, Dec 10, 2008 at 02:48:35PM -0500, Steven Rostedt wrote:
> > >
> > > Hi,
> > >
> > > In include/linux/kernel.h I currently have the following lines at the
> > > bottom of the file:
> > >
> > > /* Rebuild everything on CONFIG_FTRACE_MCOUNT_RECORD */
> > > #ifdef CONFIG_FTRACE_MCOUNT_RECORD
> > > # define REBUILD_DUE_TO_FTRACE_MCOUNT_RECORD
> > > #endif
> > >
> > >
> > > This is only there to force a rebuild of all files when
> > > CONFIG_FTRACE_MCOUNT_RECORD is modified. Since the modification of that
> > > config causes the build to act different, we need to rebuild all C
> > > objects. I added the #ifdef in kernel.h as a hack to force the rebuild by
> > > the config dependencies used in kbuild.
> > >
> > > My question is, is there a better way to force a full rebuild on a
> > > modification of a config?
> >
> > Why is that hack required in the first place?
> > We rebuild if:
> > 1- target file is missing (not the case here)
> > 2- any prerequisite files are newer than target (not the case here)
> > 3- any CONFIG_* options used by any prerequisite has changed (not the case here)
> > [It is due to your hack]
> > 4- gcc changed (not the case here)
> > 5- options are added/deleted to gcc (this should be the case for relevant files)
> >
>
> But damn me it's hard to work out where and how this is implemented :(
The magic is to be found in Kbuild.include:
# Usage: $(call if_changed_rule,foo)
# Will check if $(cmd_foo) or any of the prerequisites changed,
# and if so will execute $(rule_foo).
if_changed_rule = $(if $(strip $(any-prereq) $(arg-check) ), \
@set -e; \
$(rule_$(1)))
This parts takes care of:
$(any-prereq) takes care of 1 and 2 in the above list
$(arg-check) takes care of 4 and 5 in the above list.
And record_mcount is part of the following definition:
define rule_cc_o_c
$(call echo-cmd,checksrc) $(cmd_checksrc) \
$(call echo-cmd,cc_o_c) $(cmd_cc_o_c); \
$(cmd_modversions) \
$(cmd_record_mcount) \
scripts/basic/fixdep $(depfile) $@ '$(call make-cmd,cc_o_c)' > \
$(dot-target).tmp; \
rm -f $(depfile); \
mv -f $(dot-target).tmp $(dot-target).cmd
endef
Here we use fixdep to create a set of prerequisites - one for each
CONFIG_ symbol that is found in the prerequisites. And fixdep reads the
list of prerequisites in the $(dep-file) that is created by gcc in the
cc_o_c command:
cmd_cc_o_c = $(CC) $(c_flags) -c -o $(@D)/.tmp_$(@F) $<
So after reading this you know almost as much about kbuild as I do.
I will fix the record_mcount stuff somehow.
But not tonight. Busy with work-work.
Sam
next prev parent reply other threads:[~2008-12-10 20:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 19:48 Better way to force a rebuild Steven Rostedt
2008-12-10 20:02 ` Sam Ravnborg
2008-12-10 20:10 ` Andrew Morton
2008-12-10 20:37 ` Sam Ravnborg [this message]
2008-12-10 20:44 ` Steven Rostedt
2008-12-10 20:19 ` Steven Rostedt
2008-12-10 20:26 ` Steven Rostedt
2008-12-10 20:27 ` Steven Rostedt
2008-12-10 20:39 ` Sam Ravnborg
2008-12-10 21:28 ` Sam Ravnborg
2008-12-13 23:16 ` Sam Ravnborg
2008-12-14 17:05 ` Steven Rostedt
2008-12-16 20:06 ` Steven Rostedt
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=20081210203740.GA16674@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=zippel@linux-m68k.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