public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] buildman: allow more incremental building
Date: Wed, 4 May 2016 12:55:15 -0600	[thread overview]
Message-ID: <572A4593.3070600@wwwdotorg.org> (raw)
In-Reply-To: <1460393324-2155-1-git-send-email-swarren@wwwdotorg.org>

On 04/11/2016 10:48 AM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> One use-case for buildman is to continually run it interactively after
> each small step in a large refactoring operation. This gives more
> immediate feedback than making a number of commits and then going back and
> testing them. For this to work well, buildman needs to be extremely fast.
> At present, a couple issues prevent it being as fast as it could be:
>
> 1) Each time buildman runs "make %_defconfig", it runs "make mrproper"
> first. This throws away all previous build results, requiring a
> from-scratch build. Optionally avoiding this would speed up the build, at
> the cost of potentially causing or missing some build issues.
>
> 2) A build tree is created per thread rather than per board. When a thread
> switches between building different boards, this often causes many files
> to be rebuilt due to changing config options. Using a separate build tree
> for each board would avoid this. This does put more strain on the system's
> disk cache, but it is worth it on my system at least.
>
> This commit adds two command-line options to implement the changes
> described above; -I ("--incremental") turns of "make mrproper" and -P
> ("--per-board-out-dir") creats a build directory per board rather than per
> thread.
>
> Tested:
>
>      ./tools/buildman/buildman.py tegra
>      ./tools/buildman/buildman.py -I -P tegra
>      ./tools/buildman/buildman.py -b tegra_dev tegra
>      ./tools/buildman/buildman.py -b tegra_dev -I -P tegra
>
> ... each once after deleting the buildman result/work directory, and once
> "incrementally" after a previous identical invocation.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> Reviewed-by: Tom Rini <trini@konsulko.com>
> Acked-by: Simon Glass <sjg@chromium.org> # v1
> Tested-by: Simon Glass <sjg@chromium.org> # v1

Tom, it's been over 3 weeks since I posted this, and Simon ack'd v2.

  parent reply	other threads:[~2016-05-04 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 16:48 [U-Boot] [PATCH V2] buildman: allow more incremental building Stephen Warren
2016-04-25 16:41 ` Stephen Warren
2016-04-25 18:55   ` Simon Glass
2016-05-04 18:55 ` Stephen Warren [this message]
2016-05-04 18:58   ` Tom Rini
2016-05-04 19:09     ` Stephen Warren
2016-05-04 19:30       ` Simon Glass
2016-05-04 20:27         ` Tom Rini
2016-05-04 20:30           ` Simon Glass
2016-05-07 19:02             ` Simon Glass

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=572A4593.3070600@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /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