From: mcgrof@kernel.org (Luis R. Rodriguez)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [PATCH v3] coccinelle: fix parallel build with CHECK=scripts/coccicheck
Date: Tue, 14 Nov 2017 17:52:21 +0100 [thread overview]
Message-ID: <20171114165221.GF729@wotan.suse.de> (raw)
In-Reply-To: <1510650290-3363-1-git-send-email-yamada.masahiro@socionext.com>
On Tue, Nov 14, 2017 at 06:04:49PM +0900, Masahiro Yamada wrote:
> diff --git a/scripts/coccicheck b/scripts/coccicheck
> index 040a8b1..7da82a1 100755
> --- a/scripts/coccicheck
> +++ b/scripts/coccicheck
> @@ -70,6 +64,13 @@ if [ "$C" = "1" -o "$C" = "2" ]; then
> # Take only the last argument, which is the C file to test
> shift $(( $# - 1 ))
> OPTIONS="$COCCIINCLUDE $1"
> +
> + # If -j option is given to Make, scripts/coccicheck runs in parallel.
> + # If coccinelle also runs in parallel, it fails because multiple processes
> + # try to get access to the same subdirectory that stores stdout/stderr.
> + # No need to parallelize coccinelle in this case - this mode takes only
> + # one file input.
> + NPROC=1
Shouldn't this also warn to the user, and recommend to use a proper form to
parallelize coccinelle? Otherwise a user might get the impression they are
parallelizing coccinelle where they really did not.
Luis
> else
> ONLINE=0
> if [ "$KBUILD_EXTMOD" = "" ] ; then
WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kbuild@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr
Subject: Re: [Cocci] [PATCH v3] coccinelle: fix parallel build with CHECK=scripts/coccicheck
Date: Tue, 14 Nov 2017 17:52:21 +0100 [thread overview]
Message-ID: <20171114165221.GF729@wotan.suse.de> (raw)
In-Reply-To: <1510650290-3363-1-git-send-email-yamada.masahiro@socionext.com>
On Tue, Nov 14, 2017 at 06:04:49PM +0900, Masahiro Yamada wrote:
> diff --git a/scripts/coccicheck b/scripts/coccicheck
> index 040a8b1..7da82a1 100755
> --- a/scripts/coccicheck
> +++ b/scripts/coccicheck
> @@ -70,6 +64,13 @@ if [ "$C" = "1" -o "$C" = "2" ]; then
> # Take only the last argument, which is the C file to test
> shift $(( $# - 1 ))
> OPTIONS="$COCCIINCLUDE $1"
> +
> + # If -j option is given to Make, scripts/coccicheck runs in parallel.
> + # If coccinelle also runs in parallel, it fails because multiple processes
> + # try to get access to the same subdirectory that stores stdout/stderr.
> + # No need to parallelize coccinelle in this case - this mode takes only
> + # one file input.
> + NPROC=1
Shouldn't this also warn to the user, and recommend to use a proper form to
parallelize coccinelle? Otherwise a user might get the impression they are
parallelizing coccinelle where they really did not.
Luis
> else
> ONLINE=0
> if [ "$KBUILD_EXTMOD" = "" ] ; then
next prev parent reply other threads:[~2017-11-14 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 9:04 [Cocci] [PATCH v3] coccinelle: fix parallel build with CHECK=scripts/coccicheck Masahiro Yamada
2017-11-14 9:04 ` Masahiro Yamada
2017-11-14 9:49 ` [Cocci] " Julia Lawall
2017-11-14 9:49 ` Julia Lawall
2017-11-14 10:02 ` [Cocci] " Masahiro Yamada
2017-11-14 10:02 ` Masahiro Yamada
2017-11-14 11:09 ` [Cocci] " Julia Lawall
2017-11-14 11:09 ` Julia Lawall
2017-11-14 11:13 ` [Cocci] " Masahiro Yamada
2017-11-14 11:13 ` Masahiro Yamada
2017-11-14 16:52 ` Luis R. Rodriguez [this message]
2017-11-14 16:52 ` [Cocci] " Luis R. Rodriguez
2017-11-14 16:55 ` Julia Lawall
2017-11-14 16:55 ` Julia Lawall
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=20171114165221.GF729@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=cocci@systeme.lip6.fr \
/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.