From: Stephen Warren <swarren@wwwdotorg.org>
To: Michal Marek <mmarek@suse.cz>,
Grant Likely <glikely@secretlab.ca>,
Rob Herring <robherring2@gmail.com>
Cc: arm@kernel.org, Shawn Guo <shawn.guo@linaro.org>,
Hiroshi Doyu <hdoyu@nvidia.com>,
linux-kbuild@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH REPOST 2/7] kbuild: fixdep: support concatenated dep files
Date: Thu, 28 Mar 2013 12:00:57 -0600 [thread overview]
Message-ID: <51548559.6030605@wwwdotorg.org> (raw)
In-Reply-To: <1363890194-31538-2-git-send-email-swarren@wwwdotorg.org>
On 03/21/2013 12:23 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> The current use-case for fixdep is: a source file is run through a single
> processing step, which creates a single dependency file as a side-effect,
> which fixdep transforms into the file used by the kernel build process.
>
> In order to transparently run the C pre-processor on device-tree files,
> we wish to run both gcc -E and dtc on a source file in a single rule.
> This generates two dependency files, which must be transformed together
> into the file used by the kernel build process. This change modifies
> fixdep so it can process the concatenation of multiple separate input
> dependency files, and produce a correct unified output.
>
> The code changes have the slight benefit of transforming the loop in
> parse_dep_file() into more of a lexer/tokenizer, with the loop body being
> more of a parser. Previously, some of this logic was mixed together
> before the loop. I also added some comments, which I hope are useful.
>
> Benchmarking shows that on a cross-compiled ARM tegra_defconfig build,
> there is less than 0.5 seconds speed decrease with this change, on top
> of a build time of ~2m24s. This is probably within the noise.
Marek, do patches 2, 3, and 4 in this series look good to you from a
kbuild perspective?
I'm hoping that you can review/ack those 3 patches for kbuild, and that
Grant will review/ack the whole series, and then the series can be
merged via arm-soc for 3.10.
Let me know if you need me to repost the series again in case it's
fallen out of your inbox.
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH REPOST 2/7] kbuild: fixdep: support concatenated dep files
Date: Thu, 28 Mar 2013 12:00:57 -0600 [thread overview]
Message-ID: <51548559.6030605@wwwdotorg.org> (raw)
In-Reply-To: <1363890194-31538-2-git-send-email-swarren@wwwdotorg.org>
On 03/21/2013 12:23 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> The current use-case for fixdep is: a source file is run through a single
> processing step, which creates a single dependency file as a side-effect,
> which fixdep transforms into the file used by the kernel build process.
>
> In order to transparently run the C pre-processor on device-tree files,
> we wish to run both gcc -E and dtc on a source file in a single rule.
> This generates two dependency files, which must be transformed together
> into the file used by the kernel build process. This change modifies
> fixdep so it can process the concatenation of multiple separate input
> dependency files, and produce a correct unified output.
>
> The code changes have the slight benefit of transforming the loop in
> parse_dep_file() into more of a lexer/tokenizer, with the loop body being
> more of a parser. Previously, some of this logic was mixed together
> before the loop. I also added some comments, which I hope are useful.
>
> Benchmarking shows that on a cross-compiled ARM tegra_defconfig build,
> there is less than 0.5 seconds speed decrease with this change, on top
> of a build time of ~2m24s. This is probably within the noise.
Marek, do patches 2, 3, and 4 in this series look good to you from a
kbuild perspective?
I'm hoping that you can review/ack those 3 patches for kbuild, and that
Grant will review/ack the whole series, and then the series can be
merged via arm-soc for 3.10.
Let me know if you need me to repost the series again in case it's
fallen out of your inbox.
Thanks.
next prev parent reply other threads:[~2013-03-28 18:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 18:23 [PATCH REPOST 1/7] kbuild: create an "include chroot" for DT bindings Stephen Warren
2013-03-21 18:23 ` Stephen Warren
2013-03-21 18:23 ` [PATCH REPOST 2/7] kbuild: fixdep: support concatenated dep files Stephen Warren
2013-03-21 18:23 ` Stephen Warren
2013-03-28 18:00 ` Stephen Warren [this message]
2013-03-28 18:00 ` Stephen Warren
2013-03-21 18:23 ` [PATCH REPOST 3/7] kbuild: cmd_dtc_cpp: extract deps from both gcc -E and dtc Stephen Warren
2013-03-21 18:23 ` Stephen Warren
2013-03-21 18:23 ` Stephen Warren
2013-03-21 18:23 ` [PATCH REPOST 4/7] kbuild: always run gcc -E on *.dts, remove cmd_dtc_cpp Stephen Warren
2013-03-21 18:23 ` Stephen Warren
2013-03-21 18:23 ` Stephen Warren
2013-03-21 18:23 ` [PATCH REPOST 5/7] ARM: dt: add header to define GPIO flags Stephen Warren
2013-03-21 18:23 ` Stephen Warren
2013-03-21 18:23 ` [PATCH REPOST 6/7] ARM: dt: add header to define IRQ flags Stephen Warren
2013-03-21 18:23 ` Stephen Warren
2013-03-21 18:23 ` [PATCH REPOST 7/7] ARM: dt: create a DT header for the GIC Stephen Warren
2013-03-21 18:23 ` Stephen Warren
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=51548559.6030605@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arm@kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=glikely@secretlab.ca \
--cc=hdoyu@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=robherring2@gmail.com \
--cc=shawn.guo@linaro.org \
--cc=swarren@nvidia.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 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.