All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Fam Zheng" <famz@redhat.com>, "Eric Blake" <eblake@redhat.com>,
	qemu-devel@nongnu.org,
	"Daniel P . Berrange" <berrange@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] Makefile: Enable synchronized parallel output when possible
Date: Fri, 22 Jun 2018 06:22:03 +0300	[thread overview]
Message-ID: <20180622061513-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180622022035.18490-1-f4bug@amsat.org>

On Thu, Jun 21, 2018 at 11:20:35PM -0300, Philippe Mathieu-Daudé wrote:
> The '--output-sync' option is available since GNU make 4.0.
> 
>   5.4.1 Output During Parallel Execution
> 
>   When running several recipes in parallel the output from each
>   recipe appears as soon as it is generated, with the result that
>   messages from different recipes may be interspersed, sometimes
>   even appearing on the same line. This can make reading the output
>   very difficult.
> 
>   To avoid this you can use the ‘--output-sync’ (‘-O’) option. This
>   option instructs make to save the output from the commands it
>   invokes and print it all once the commands are completed.
>   Additionally, if there are multiple recursive make invocations
>   running in parallel, they will communicate so that only one of
>   them is generating output at a time.
> 
>   There are four levels of granularity when synchronizing output,
>   specified by giving an argument to the option (e.g., ‘-Oline’
>   or ‘--output-sync=recurse’).
> 
>     none
>       This is the default: all output is sent directly as it is
>       generated and no synchronization is performed.
> 
>     line
>       Output from each individual line of the recipe is grouped
>       and printed as soon as that line is complete. If a recipe
>       consists of multiple lines, they may be interspersed with
>       lines from other recipes.
> 
>     target
>       Output from the entire recipe for each target is grouped and
>       printed once the target is complete. This is the default if
>       the --output-sync or -O option is given with no argument.
> 
>     recurse
>       Output from each recursive invocation of make is grouped and
>       printed once the recursive invocation is complete.
> 
>   Regardless of the mode chosen, the total build time will be the
>   same. The only difference is in how the output appears.
> 
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> Maybe 'line' is better for workstation and 'target/recurse' for
> unattended builds.
> 
> doc: https://www.gnu.org/software/make/manual/html_node/Parallel-Output.html
> ---
>  Makefile | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Makefile b/Makefile
> index e46f2b625a..e94c687afe 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -367,6 +367,10 @@ DOCS=
>  endif
>  
>  SUBDIR_MAKEFLAGS=$(if $(V),,--no-print-directory --quiet) BUILD_DIR=$(BUILD_DIR)
> +ifeq ($(shell test $(firstword $(subst ., ,$(MAKE_VERSION))) -ge 4; echo $$?),0)
> +SUBDIR_MAKEFLAGS+=--output-sync=target
> +endif
> +
>  SUBDIR_DEVICES_MAK=$(patsubst %, %/config-devices.mak, $(TARGET_LIST))
>  SUBDIR_DEVICES_MAK_DEP=$(patsubst %, %-config-devices.mak.d, $(TARGET_LIST))

I'd probably just use -O. If they change the default it will probably be
to a better one.

> -- 
> 2.18.0.rc2

  reply	other threads:[~2018-06-22  3:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  2:20 [Qemu-devel] [RFC PATCH] Makefile: Enable synchronized parallel output when possible Philippe Mathieu-Daudé
2018-06-22  3:22 ` Michael S. Tsirkin [this message]
2018-06-25 16:12   ` Paolo Bonzini
2018-06-25 16:33 ` Peter Maydell

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=20180622061513-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=famz@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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 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.