linux-kernel - arm/arm64 perf build issue with mainline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150423112916.GF1652@arm.com>
Date:	Thu, 23 Apr 2015 12:29:17 +0100
From:	Will Deacon <will.deacon@....com>
To:	david.ahern@...cle.com
Cc:	linux-kernel@...r.kernel.org, mark.rutland@....com,
	jolsa@...nel.org, namhyung@...nel.org, acme@...hat.com
Subject: arm/arm64 perf build issue with mainline

Hi all,

Commit 6428c59a97de ("perf tools: Set JOBS based on CPU or processor")
causes weird behaviour on arm/arm64 platforms because we use the "CPU"
prefix for things like:

CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x0
CPU part        : 0xd03
CPU revision    : 0

in /proc/cpuinfo. Consequently, a 6 core machine ends up doing:

will@...finement-loaf:~/linux/tools/perf$ make
  BUILD:   Doing 'make -j36' parallel build

which is a little overwhelming. Any chance we can predicate the extra
part of the regex on $(ARCH) being sparc?

Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/