From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Jan Kiszka" <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] Consolidate over PARALLEL_MAKE
Date: Wed, 3 Jun 2020 11:49:46 +0200 [thread overview]
Message-ID: <20200603114946.3f1db38c@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <ced41f47-0071-9c16-a54f-29853cd5343a@siemens.com>
On Wed, 3 Jun 2020 08:37:57 +0200
"[ext] Jan Kiszka" <jan.kiszka@siemens.com> wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Replace self-invented / open-coded parallel build rules over the OE
> pattern PARALLEL_MAKE. Should specifically reduce the spread of
> PARALLEL_BUILD definitions in downstream layers. Mea culpa.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules | 5 ++---
> meta/classes/dpkg.bbclass | 1 +
> meta/conf/bitbake.conf | 4 ++++
> meta/recipes-bsp/u-boot/files/debian/rules | 8 +++-----
> meta/recipes-kernel/linux/files/debian/isar/build.tmpl | 2 +-
> 5 files changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules
> b/meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules index
> c8feb715..c3fc50a9 100644 ---
> a/meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules +++
> b/meta-isar/recipes-bsp/opensbi/files/sifive-fu540-rules @@ -4,10
> +4,9 @@ ifneq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE)) export
> CROSS_COMPILE=$(DEB_HOST_GNU_TYPE)- endif
>
> -PARALLEL_BUILD=-j $(shell echo $$(($$(nproc) * 2)))
> -
> override_dh_auto_build:
> - CFLAGS= LDFLAGS= $(MAKE) $(PARALLEL_BUILD)
> PLATFORM=sifive/fu540
> FW_PAYLOAD_PATH=/usr/lib/u-boot/sifive_fu540/u-boot.bin
> + CFLAGS= LDFLAGS= $(MAKE) $(PARALLEL_MAKE)
> PLATFORM=sifive/fu540 \
> +
> FW_PAYLOAD_PATH=/usr/lib/u-boot/sifive_fu540/u-boot.bin
> %:
> dh $@
> diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
> index 585365ee..acccc1f2 100644
> --- a/meta/classes/dpkg.bbclass
> +++ b/meta/classes/dpkg.bbclass
> @@ -25,6 +25,7 @@ addtask devshell after do_install_builddeps
> # Build package from sources using build script
> dpkg_runbuild() {
> E="${@ isar_export_proxies(d)}"
> + export PARALLEL_MAKE="${PARALLEL_MAKE}"
> sudo -E chroot --userspec=$( id -u ):$( id -g )
> ${BUILDCHROOT_DIR} \ /isar/build.sh ${PP}/${PPS} ${DISTRO_ARCH}
> }
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 848e085a..0e0c79e0 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -101,8 +101,12 @@ BB_HASHCONFIG_WHITELIST ?=
> "${BB_HASHBASE_WHITELIST} DATE TIME SSH_AGENT_PID \
> BB_SIGNATURE_HANDLER ?= "basichash" BB_STAMP_POLICY ?= "full"
>
> +# Default to setting automatically based on cpu count
> BB_NUMBER_THREADS ?= "${@bb.utils.cpu_count()}"
>
> +# Default to setting automatically based on cpu count
> +PARALLEL_MAKE ?= "-j ${@bb.utils.cpu_count()}"
Maybe derive it from the other one "-j ${BB_NUMBER_THREADS}" ?
For make it is often suggested to use slightly more threads than
available CPUs, when some threads are doing IO you still get to use all
CPUs. There was a "*2" ...
Henning
> BBINCLUDELOGS ??= "yes"
>
> # Add event handlers for bitbake
> diff --git a/meta/recipes-bsp/u-boot/files/debian/rules
> b/meta/recipes-bsp/u-boot/files/debian/rules index 3f7a3218..92c07b17
> 100755 --- a/meta/recipes-bsp/u-boot/files/debian/rules
> +++ b/meta/recipes-bsp/u-boot/files/debian/rules
> @@ -12,12 +12,10 @@ export CROSS_COMPILE=$(DEB_HOST_GNU_TYPE)-
> SET_CROSS_BUILD_TOOLS=CROSS_BUILD_TOOLS=y
> endif
>
> -PARALLEL_BUILD=-j $(shell echo $$(($$(nproc) * 2)))
> -
> override_dh_auto_build:
> - $(MAKE) $(PARALLEL_BUILD) $(U_BOOT_CONFIG)
> - $(MAKE) $(PARALLEL_BUILD) ${U_BOOT_BIN}
> - $(MAKE) $(PARALLEL_BUILD) $(SET_CROSS_BUILD_TOOLS) NO_SDL=1
> tools-only envtools
> + $(MAKE) $(PARALLEL_MAKE) $(U_BOOT_CONFIG)
> + $(MAKE) $(PARALLEL_MAKE) ${U_BOOT_BIN}
> + $(MAKE) $(PARALLEL_MAKE) $(SET_CROSS_BUILD_TOOLS) NO_SDL=1
> tools-only envtools
> override_dh_auto_install:
> mv tools/env/lib.a tools/env/libubootenv.a
> diff --git a/meta/recipes-kernel/linux/files/debian/isar/build.tmpl
> b/meta/recipes-kernel/linux/files/debian/isar/build.tmpl index
> 17983e4d..b7749cec 100644 ---
> a/meta/recipes-kernel/linux/files/debian/isar/build.tmpl +++
> b/meta/recipes-kernel/linux/files/debian/isar/build.tmpl @@ -22,7
> +22,7 @@ do_build() { set -x
>
> # Build the Linux kernel
> - ${MAKE} O=${KERNEL_BUILD_DIR} -j $(nproc) || exit ${?}
> + ${MAKE} O=${KERNEL_BUILD_DIR} ${PARALLEL_MAKE} || exit ${?}
>
> # Stop tracing
> set +x
next prev parent reply other threads:[~2020-06-03 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 6:37 Jan Kiszka
2020-06-03 9:49 ` Henning Schild [this message]
2020-06-03 9:56 ` Jan Kiszka
2020-06-21 19:02 ` Baurzhan Ismagulov
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=20200603114946.3f1db38c@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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