From: Paolo Bonzini <pbonzini@redhat.com>
To: Daniele Buono <dbuono@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH 1/2] gitlab-ci.yml: Allow custom make parallelism
Date: Tue, 23 Feb 2021 09:12:37 +0100 [thread overview]
Message-ID: <20057039-92b4-5b0f-436d-7310e9e59dfe@redhat.com> (raw)
In-Reply-To: <20210222230106.7030-2-dbuono@linux.vnet.ibm.com>
On 23/02/21 00:01, Daniele Buono wrote:
> Currently, make parallelism at build time is defined as #cpus+1. Some
> build jobs may need (or benefit from) a different number. An example is
> builds with LTO where, because of the huge demand of memory at link
> time, gitlab runners fails if two linkers are run concurrently This
> patch retains the default value of #cpus+1 but allows setting the "JOBS"
> variable to a different number when applying the template
As I just found out, you can add -Dbackend_max_links=1 to the meson
command line instead if LTO is enabled.
Paolo
next prev parent reply other threads:[~2021-02-23 8:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 23:01 [PATCH 0/2] gitlab-ci.yml: Add jobs to test CFI Daniele Buono
2021-02-22 23:01 ` [PATCH 1/2] gitlab-ci.yml: Allow custom make parallelism Daniele Buono
2021-02-23 8:12 ` Paolo Bonzini [this message]
2021-02-23 19:34 ` Daniele Buono
2021-02-24 7:44 ` Paolo Bonzini
2021-02-24 18:02 ` Daniele Buono
2021-02-23 15:03 ` Wainer dos Santos Moschetta
2021-02-22 23:01 ` [PATCH 2/2] gitlab-ci.yml: Add jobs to test CFI flags Daniele Buono
2021-02-23 8:11 ` Paolo Bonzini
2021-02-24 17:55 ` Daniele Buono
2021-02-24 18:28 ` Paolo Bonzini
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=20057039-92b4-5b0f-436d-7310e9e59dfe@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=dbuono@linux.vnet.ibm.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.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.