Changes in PERF-VERSION-GEN

f24fb539 - perf tools: Don't include signature in version strings

Tue, 27 Dec 2022 20:58:00 +0000

perf tools: Don't include signature in version stringsThis explodes the build if HEAD is signed, since the generated versionis gpg: Signature made Mon 26 Dec 2022 20:34:48 CET, then a few morelines, then the SHA.Signed-off-by: Ahelenia Ziemiańska Acked-by: Namhyung Kim Cc: Alexander Shishkin Cc: Jiri Olsa Cc: Mark Rutland Cc: Peter Zijlstra Link: http://lore.kernel.org/lkml/7c9637711271f50ec2341fb8a7c29585335dab04.1672174189.git.nabijaczleweli@nabijaczleweli.xyzSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

81935f10 - perf tools: Fix empty version number when building outside of a git repo

Fri, 30 Sep 2022 15:11:57 +0000

perf tools: Fix empty version number when building outside of a git repoWhen perf is built in a full source tree that is not a git repository,e.g. from a kernel source tarball, `perf version` will print empty tagand commit strings: $ perf version perf versionCurrently the tag version is only generated from the root Makefile whenbuilding in a git repository. If PERF-VERSION-FILE has not beengenerated and the source tree is not in a git repository, thenPERF-VERSION-GEN will return an empty version.The problem can be reproduced with the following steps: $ wget https://git.kernel.org/torvalds/t/linux-6.0-rc7.tar.gz $ tar -xf linux-6.0-rc7.tar.gz && cd linux-6.0-rc7 $ make -C tools/perf $ tools/perf/perf -v perf versionBuilds from tarballs generated with `make perf-tar-src-pkg` are notimpacted by this issue as PERF-VERSION-FILE is included in the archive.The perf RPM provided by Fedora for 5.18+ is experiencing this problem.Package build logs[0] show that the build is attempting to fall back onPERF-VERSION-FILE, but it is not present.To resolve this, revert back to the previous logic of using the kernelMakefile version if not in a git repository and PERF-VERSION-FILE doesnot exist.[0] https://kojipkgs.fedoraproject.org/packages/kernel-tools/5.19.4/200.fc36/data/logs/x86_64/build.logFixes: 7572733b84997d23 ("perf tools: Fix version kernel tag")Reviewed-by: John Garry Signed-off-by: Will Chandler Tested-by: Arnaldo Carvalho de Melo Cc: Alexander Shishkin Cc: Ingo Molnar Cc: Jiri Olsa Cc: John Garry Cc: Mark Rutland Cc: Namhyung Kim Cc: Peter Zijlstra Link: https://lore.kernel.org/r/20220930151157.529674-1-wfc@wfchandler.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

7572733b - perf tools: Fix version kernel tag

Mon, 21 Feb 2022 13:16:49 +0000

perf tools: Fix version kernel tagGenerating the version kernel tag relies on "git describe" command toget the latest Linus kernel tag.However, when working from clones of Linus' git we may not have the latesttag. For example, when working on Arnaldo's acme.git, we can have this: $ git branch perf/core $ head -n 5 ../../Makefile | tail -n 4 VERSION = 5 PATCHLEVEL = 17 SUBLEVEL = 0 EXTRAVERSION = -rc3 $ git describe --abbrev=0 --match "v[0-9].[0-9]*" v4.13-rc5Indeed using tags is a problem as it relies on tags being pulled fromLinus' git (and pushed to the clone).In commit a4147f0f91386540 ("perf tools: Fix perf version generation")Robert introduced a change to use the kernelversion rule to generate thekernel tag when no git tags are available.However, as mentioned above, the tag we generate may be incorrect, sojust always use kernelversion to get the tag (apart from building perfout of tree).Signed-off-by: John Garry Tested-by: Arnaldo Carvalho de Melo Acked-by: Ian Rogers Cc: Alexander Shishkin Cc: Andi Kleen Cc: Ingo Molnar Cc: Jiri Olsa Cc: Mark Rutland Cc: Namhyung Kim Cc: Peter Zijlstra Cc: Robert Richter Link: https://lore.kernel.org/r/1645449409-158238-3-git-send-email-john.garry@huawei.comSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

80ec26d1 - perf version: Append 12 git SHA chars to the version string

Fri, 24 May 2019 18:50:18 +0000

perf version: Append 12 git SHA chars to the version stringBumping it from just 4:Before: $ perf -v perf version 5.2.rc1.g80978f $After: $ perf -v perf version 5.2.rc1.g80978fc864c5 $Requested-by: Ingo Molnar Cc: Adrian Hunter Cc: Jiri Olsa Cc: Namhyung Kim Link: https://lkml.kernel.org/n/tip-p4yun2nxlo7eeeohyx5v4kw7@git.kernel.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

a614d01b - perf tools: Fix version when building out of tree

Wed, 06 Nov 2013 15:55:35 +0000

perf tools: Fix version when building out of treeWhen building perf out of tree: $ make perf-tar-src-pkg $ tar -xf perf-.tar -C /tmp $ cd /tmp/perf $ make -C tools/perfyou get this warning message: make[1]: *** No rule to make target `kernelversion'. Stop.Fix it by saving the perf version in the tar file and using that for theout of tree builds.v2: removed short form request and fixed up version string from usual output.Signed-off-by: David Ahern Suggested-by: Ingo Molnar Cc: Ingo Molnar Cc: Jiri Olsa Cc: Namhyung Kim Link: http://lkml.kernel.org/r/1383753335-25782-1-git-send-email-dsahern@gmail.comSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

3fae82db - perf tools: Align perf version output to other build messages

Wed, 09 Oct 2013 09:49:28 +0000

perf tools: Align perf version output to other build messagesBefore: CC util/pmu.o CC util/parse-events.oPERF_VERSION = 3.12.rc4.g1b30c CC util/parse-events-flex.o GEN perf-archiveAfter: CC util/pmu.o CC util/parse-events.o PERF_VERSION = 3.12.rc4.g1b30c CC util/parse-events-flex.o GEN perf-archiveSigned-off-by: Ingo Molnar Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/1381312169-17354-4-git-send-email-mingo@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

a4147f0f - perf tools: Fix perf version generation

Wed, 08 May 2013 09:43:34 +0000

perf tools: Fix perf version generationThe tag of the perf version is wrongly determined, always the latest tagis taken regardless of the HEAD commit: $ perf --version perf version 3.9.rc8.gd7f5d3 $ git describe d7f5d3 v3.9-rc7-154-gd7f5d33 $ head -n 4 Makefile VERSION = 3 PATCHLEVEL = 9 SUBLEVEL = 0 EXTRAVERSION = -rc7In other cases no tag might be found.This patch fixes this.This new implementation handles also the case if there are no tags atall found in the git repo but there is a commit id.Signed-off-by: Robert Richter Link: http://lkml.kernel.org/r/1368006214-12912-1-git-send-email-rric@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

3cecaa20 - perf tools: Do not include PERF-VERSION-FILE to Makefile

Wed, 16 Jan 2013 11:59:53 +0000

perf tools: Do not include PERF-VERSION-FILE to MakefileWhen make runs it tries to update the Makefile rules by reading all ofincluded Makefiles. During the perf build it checks PERF-VERSION-FILEto get the current version number. But it triggers Makefile update sothat make runs again with the update Makefile and, in turn, users willsee duplicate CHK message on the second path.Running make with -d option for debugging tells me this:GNU Make 3.82Built for x86_64-redhat-linux-gnuCopyright (C) 2010 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law.Reading makefiles...Reading makefile `Makefile'...Reading makefile `../scripts/Makefile.include' (search path) (no ~ expansion)...Reading makefile `config/utilities.mak' (search path) (no ~ expansion)...Reading makefile `PERF-VERSION-FILE' (search path) (don't care) (no ~ expansion)...Reading makefile `config/feature-tests.mak' (search path) (don't care) (no ~ expansion)... CHK -fstack-protector-all CHK -Wstack-protector CHK -Wvolatile-register-var...Updating makefiles.... Considering target file `PERF-VERSION-FILE'. Must remake target `PERF-VERSION-FILE'.Invoking recipe from Makefile:52 to update target `PERF-VERSION-FILE'.Putting child 0x14037a0 (PERF-VERSION-FILE) PID 31925 on the chain.Live child 0x14037a0 (PERF-VERSION-FILE) PID 31925PERF_VERSION = 3.8.rc3.gf751db6Reaping winning child 0x14037a0 PID 31925Removing child 0x14037a0 PID 31925 from chain. Successfully remade target file `PERF-VERSION-FILE'....Re-executing[1]: make -d <------------ hereGNU Make 3.82Built for x86_64-redhat-linux-gnuCopyright (C) 2010 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law.Reading makefiles...Reading makefile `Makefile'...Reading makefile `../scripts/Makefile.include' (search path) (no ~ expansion)...Reading makefile `config/utilities.mak' (search path) (no ~ expansion)...Reading makefile `PERF-VERSION-FILE' (search path) (don't care) (no ~ expansion)...Reading makefile `config/feature-tests.mak' (search path) (don't care) (no ~ expansion)... CHK -fstack-protector-all CHK -Wstack-protector CHK -Wvolatile-register-var...Actually PERF-VERSION-FILE is used only for perf.c to #definePERF_VERSION macro. So make it like a C header file and include itduring compiling the perf.c file will remove the need of beingincluded into Makefile. Hench no need to update the Makefile and noCHK lines anymore.Signed-off-by: Namhyung Kim Cc: Ingo Molnar Cc: Paul Mackerras Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/1358337594-10916-1-git-send-email-namhyung@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

688b2c2f - perf tools: Handle --version string generation on machines without git

Tue, 30 Oct 2012 15:44:40 +0000

perf tools: Handle --version string generation on machines without gitIf git is installed we'll have a 'perf --version' output of this form:$ make -j8 -C tools/perf/ O=/home/acme/git/build/perf install$ perf --versionperf version 3.7.rc3.g3afad6Now on a machine without git installed:$ mv /home/acme/bin/git /home/acme/bin/git.OFF$ make -j8 -C tools/perf/ O=/home/acme/git/build/perf install$ perf --versionperf version 3.7.0-rc2That is, no error message due to git not being installed will appear on thescreen and instead the version string in the top level Makefile will beused.Requested-by: Ingo Molnar Cc: David Ahern Cc: Frederic Weisbecker Cc: Jiri Olsa Cc: Mike Galbraith Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Cc: Stephane Eranian Link: http://lkml.kernel.org/n/tip-am6yp6phvxyjmyndxogpunjv@git.kernel.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

0e2af956 - perf tools: Further speed up the perf build

Tue, 30 Oct 2012 08:54:41 +0000

perf tools: Further speed up the perf buildThere's another source of overhead in the perf version string generator: git update-index -q --refresh... which will iterate the whole checked out tree. This can be prettyslow on NFS volumes, but takes some time even with local SSD disks and afully cached kernel tree: $ perf stat --null --repeat 3 --pre "rm -f PERF-VERSION-FILE" util/PERF-VERSION-GEN PERF_VERSION = 3.7.rc3.g5399b3b.dirty PERF_VERSION = 3.7.rc3.g5399b3b.dirty PERF_VERSION = 3.7.rc3.g5399b3b.dirty Performance counter stats for 'util/PERF-VERSION-GEN' (3 runs): 0.306999221 seconds time elapsed ( +- 0.56% )So remove the .dirty differentiator as well - it adds little informationbecause locally patched git trees are common, but seldom are the perftools modified.So a lot of version strings are reported as 'dirty' while in fact theyare pristine perf builds. For example 99% of my perf builds are notpatched but the kernel tree is slightly patched, which adds the .dirtytag.Eliminating that tag speeds up version generation by another order ofmagnitude: $ perf stat --null --repeat 3 --sync --pre "rm -f PERF-VERSION-FILE" util/PERF-VERSION-GEN PERF_VERSION = 3.7.rc3.g4b0bd3 PERF_VERSION = 3.7.rc3.g4b0bd3 PERF_VERSION = 3.7.rc3.g4b0bd3 Performance counter stats for 'util/PERF-VERSION-GEN' (3 runs): 0.021270923 seconds time elapsed ( +- 1.94% )(Also clean up some of the comments around this code.)Signed-off-by: Ingo Molnar Cc: Andrew Vagin Cc: Borislav Petkov Cc: David Howells Cc: Frederic Weisbecker Cc: Jiri Olsa Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Cc: Stephane Eranian Cc: Steven Rostedt Link: http://lkml.kernel.org/r/20121030085441.GC8245@gmail.comSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

acddedfb - perf tools: Speed up the perf build time by simplifying the perf --version string generation

Tue, 30 Oct 2012 08:46:00 +0000

perf tools: Speed up the perf build time by simplifying the perf --version string generationBuilding perf is pretty slow on trees that have a lot of commitsrelative to the nearest Git tag. This slowness manifests itself duringversion string generation: $ perf stat --null --repeat 3 --sync --pre "rm -f PERF-VERSION-FILE" util/PERF-VERSION-GEN PERF_VERSION = 3.7.rc3.1458.g5399b3b PERF_VERSION = 3.7.rc3.1458.g5399b3b PERF_VERSION = 3.7.rc3.1458.g5399b3b Performance counter stats for 'util/PERF-VERSION-GEN' (3 runs): 2.857503976 seconds time elapsed ( +- 0.22% )The build can be even slower than that, when one over NFS volumes.The reason for the slowness is that util/PERF-VERSION-GEN uses "gitdescribe" to generate the string, which has to count the "number ofcommits distance" from the nearest tag - the ".1458." count in theoutput above. For that Git had to extract and decompress 1458 Gitobjects, which takes time and bandwidth.But this "number of commits" value is mostly irrelevant in practice. Weeither want to know an approximate tag name, or we want to know theprecise sha1.So this patch simplifies the version string to: PERF_VERSION = 3.7.rc3.g5399b3b.dirtywhich speeds up the version string generation script by an order ofmagnitude: $ perf stat --null --repeat 3 --sync --pre "rm -f PERF-VERSION-FILE" util/PERF-VERSION-GEN PERF_VERSION = 3.7.rc3.g5399b3b.dirty PERF_VERSION = 3.7.rc3.g5399b3b.dirty PERF_VERSION = 3.7.rc3.g5399b3b.dirty Performance counter stats for 'util/PERF-VERSION-GEN' (3 runs): 0.307633559 seconds time elapsed ( +- 0.84% )Signed-off-by: Ingo Molnar Cc: Andrew Vagin Cc: Borislav Petkov Cc: David Howells Cc: Frederic Weisbecker Cc: Jiri Olsa Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Cc: Stephane Eranian Cc: Steven Rostedt Link: http://lkml.kernel.org/r/20121030084600.GB8245@gmail.comSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

aa5cdd30 - perf tools: Make --version show kernel version instead of pull req tag

Thu, 31 May 2012 14:17:34 +0000

perf tools: Make --version show kernel version instead of pull req tagBefore: $ perf --version perf version perf.urgent.for.mingo.5.g37da28After: $ perf --version perf version 3.4.8941.g37da28.dirtyCc: David Ahern Cc: Frederic Weisbecker Cc: Jiri Olsa Cc: Mike Galbraith Cc: Namhyung Kim Cc: Paul Mackerras Cc: Peter Zijlstra Cc: Stephane Eranian Link: http://lkml.kernel.org/n/tip-vc9b4e6023iegz9kabr3yvyv@git.kernel.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

37aa9a2e - perf: clear out make flags when calling kernel make kernelver

Wed, 15 Jun 2011 13:35:00 +0000

perf: clear out make flags when calling kernel make kernelverWhen generating the perf version from the kernel version using 'makekernelver' it is necessary to clear out any MAKEFLAGS otherwise they maytrigger additional output which pollute the contents.Signed-off-by: Andy Whitcroft Signed-off-by: Michal Marek List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

5d61b9fd - perf: Use make kernelversion instead of parsing the Makefile

Mon, 30 May 2011 12:12:09 +0000

perf: Use make kernelversion instead of parsing the MakefileCc: Peter Zijlstra Cc: Paul Mackerras Cc: Ingo Molnar Cc: Arnaldo Carvalho de Melo Signed-off-by: Michal Marek List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

58d406ed - perf tools: Version incorrect with some versions of grep

Wed, 16 Mar 2011 02:16:40 +0000

perf tools: Version incorrect with some versions of grepSome versions of grep don't treat '\s' properly. When building perf on suchsystems and using a kernel tarball the perf version is unable to be determinedfrom the main kernel Makefile and the user is left with a version of '..'.Replacing the use of '\s' with '[[:space:]]', which should work in all grepversions, gives a usable version number.Reported-by: Tapan Dhimant Cc: Ingo Molnar Cc: Paul Mackerras Cc: Peter Zijlstra Cc: Tapan Dhimant Cc: linux-kernel@vger.kernel.orgCc: stable@kernel.orgLKML-Reference: <1300241800-30281-1-git-send-email-johunt@akamai.com>Signed-off-by: Josh Hunt Signed-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

869599ce - perf: Version String fix, for fallback if not from git

Mon, 05 Jul 2010 08:00:15 +0000

perf: Version String fix, for fallback if not from gitThis gets rid of the default version fallback for Perf andchanges it so that it returns the version of the kernel fromit's Makefile (if sources were not from git, ie. if it wasdownloaded from a tarball)Signed-off-by: Thavidu Ranatunga Acked-by: Ian Munsie Acked-by: Peter Zijlstra Cc: Paul Mackerras Cc: Arnaldo Carvalho de Melo LKML-Reference: <1278316815-6099-2-git-send-email-tharan@au1.ibm.com>Signed-off-by: Ingo Molnar List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

2190de2f - perf: Version String fix, using kernel version

Mon, 05 Jul 2010 08:00:14 +0000

perf: Version String fix, using kernel versionChanges the Perf --version string such that it shows the kernelversion as suggested by Ingo as follows:That way the perf that comes with v2.6.34 will be: perf version v2.6.34while interim versions will have the version of the interimkernel - for example: perf version v2.6.35-rc4-70-g39ef13aThis functionality was already in the perf version generatorfile except that it was looking for a .git in the perf directoryinstead of the kernel directory.Signed-off-by: Thavidu Ranatunga Acked-by: Ian Munsie Acked-by: Peter Zijlstra Cc: Paul Mackerras Cc: Arnaldo Carvalho de Melo LKML-Reference: <1278316815-6099-1-git-send-email-tharan@au1.ibm.com>Signed-off-by: Ingo Molnar List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

c29ede61 - perf tools: Allow specifying O= to build files in a separate directory

Sat, 27 Mar 2010 17:30:45 +0000

perf tools: Allow specifying O= to build files in a separate directoryAvoiding polluting the source tree with build files.Reported-by: Steven Rostedt Cc: Steven Rostedt Cc: Frédéric Weisbecker Cc: Mike Galbraith Cc: Peter Zijlstra Cc: Paul Mackerras Signed-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN

210f9cb2 - perf tools: Bump version to 0.0.2

Fri, 16 Oct 2009 08:34:28 +0000

perf tools: Bump version to 0.0.2We released the first version of perf with 0.0.1 in v2.6.31,time to double our version number to 0.0.2 ;-)Cc: Peter Zijlstra Cc: Mike Galbraith Cc: Paul Mackerras Cc: Arnaldo Carvalho de Melo Cc: Frederic Weisbecker LKML-Reference: Signed-off-by: Ingo Molnar List of files: /linux-6.15/tools/perf/util/PERF-VERSION-GEN