Changes in Makefile

703fb765 - perf/x86/amd/lbr: Detect LbrExtV2 support

Thu, 11 Aug 2022 12:29:53 +0000

perf/x86/amd/lbr: Detect LbrExtV2 supportAMD Last Branch Record Extension Version 2 (LbrExtV2) is driven by Core PMCoverflows. It records recently taken branches up to the moment when the PMCoverflow occurs.Detect the feature during PMU initialization and set the branch stack depthusing CPUID leaf 0x80000022 EBX.Signed-off-by: Sandipan Das Signed-off-by: Peter Zijlstra (Intel) Link: https://lore.kernel.org/r/fc6e45378ada258f1bab79b0de6e05c393a8f1dd.1660211399.git.sandipan.das@amd.com List of files: /linux-6.15/arch/x86/events/amd/Makefile

cc37e520 - perf/x86/amd: Make Zen3 branch sampling opt-in

Tue, 22 Mar 2022 22:15:11 +0000

perf/x86/amd: Make Zen3 branch sampling opt-inAdd a kernel config option CONFIG_PERF_EVENTS_AMD_BRSto make the support for AMD Zen3 Branch Sampling (BRS) an opt-incompile time option.Signed-off-by: Stephane Eranian Signed-off-by: Peter Zijlstra (Intel) Link: https://lore.kernel.org/r/20220322221517.2510440-8-eranian@google.com List of files: /linux-6.15/arch/x86/events/amd/Makefile

ada54345 - perf/x86/amd: Add AMD Fam19h Branch Sampling support

Tue, 22 Mar 2022 22:15:07 +0000

perf/x86/amd: Add AMD Fam19h Branch Sampling supportAdd support for the AMD Fam19h 16-deep branch sampling feature asdescribed in the AMD PPR Fam19h Model 01h Revision B1. This is a modelspecific extension. It is not an architected AMD feature.The Branch Sampling (BRS) operates with a 16-deep saturating buffer in MSRregisters. There is no branch type filtering. All control flow changes arecaptured. BRS relies on specific programming of the core PMU of Fam19h. Inparticular, the following requirements must be met: - the sampling period be greater than 16 (BRS depth) - the sampling period must use a fixed and not frequency modeBRS interacts with the NMI interrupt as well. Because enabling BRS isexpensive, it is only activated after P event occurrences, where P is thedesired sampling period. At P occurrences of the event, the counteroverflows, the CPU catches the interrupt, activates BRS for 16 branches untilit saturates, and then delivers the NMI to the kernel. Between the overflowand the time BRS activates more branches may be executed skewing the period.All along, the sampling event keeps counting. The skid may be attenuated byreducing the sampling period by 16 (subsequent patch).BRS is integrated into perf_events seamlessly via the samePERF_RECORD_BRANCH_STACK sample format. BRS generates perf_branch_entryrecords in the sampling buffer. No prediction information is supported. Thebranches are stored in reverse order of execution. The most recent branch isthe first entry in each record.No modification to the perf tool is necessary.BRS can be used with any sampling event. However, it is recommended to usethe RETIRED_BRANCH_INSTRUCTIONS event because it matches what the BRScaptures.$ perf record -b -c 1000037 -e cpu/event=0xc2,name=ret_br_instructions/ test$ perf report -D56531696056126 0x193c000 [0x1a8]: PERF_RECORD_SAMPLE(IP, 0x2): 18122/18230: 0x401d24 period: 1000037 addr: 0... branch stack: nr:16..... 0: 0000000000401d24 -> 0000000000401d5a 0 cycles 0..... 1: 0000000000401d5c -> 0000000000401d24 0 cycles 0..... 2: 0000000000401d22 -> 0000000000401d5c 0 cycles 0..... 3: 0000000000401d5e -> 0000000000401d22 0 cycles 0..... 4: 0000000000401d20 -> 0000000000401d5e 0 cycles 0..... 5: 0000000000401d3e -> 0000000000401d20 0 cycles 0..... 6: 0000000000401d42 -> 0000000000401d3e 0 cycles 0..... 7: 0000000000401d3c -> 0000000000401d42 0 cycles 0..... 8: 0000000000401d44 -> 0000000000401d3c 0 cycles 0..... 9: 0000000000401d3a -> 0000000000401d44 0 cycles 0..... 10: 0000000000401d46 -> 0000000000401d3a 0 cycles 0..... 11: 0000000000401d38 -> 0000000000401d46 0 cycles 0..... 12: 0000000000401d48 -> 0000000000401d38 0 cycles 0..... 13: 0000000000401d36 -> 0000000000401d48 0 cycles 0..... 14: 0000000000401d4a -> 0000000000401d36 0 cycles 0..... 15: 0000000000401d34 -> 0000000000401d4a 0 cycles 0 ... thread: test:18230 ...... dso: testSigned-off-by: Stephane Eranian Signed-off-by: Peter Zijlstra (Intel) Link: https://lore.kernel.org/r/20220322221517.2510440-4-eranian@google.com List of files: /linux-6.15/arch/x86/events/amd/Makefile

05485745 - perf/amd/uncore: Allow the driver to be built as a module

Tue, 17 Aug 2021 22:10:47 +0000

perf/amd/uncore: Allow the driver to be built as a moduleAdd support to build the AMD uncore driver as a module.This is in order to facilitate development without havingto reboot the kernel in most cases.Signed-off-by: Kim Phillips Signed-off-by: Peter Zijlstra (Intel) Signed-off-by: Ingo Molnar Link: https://lore.kernel.org/r/20210817221048.88063-8-kim.phillips@amd.com List of files: /linux-6.15/arch/x86/events/amd/Makefile

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/arch/x86/events/amd/Makefile

612f0c0b - perf/x86/events: Add an AMD-specific Makefile

Thu, 26 Jan 2017 08:08:19 +0000

perf/x86/events: Add an AMD-specific MakefileMove the AMD pieces from the generic Makefile so that $ make arch/x86/events/amd/.scan work too. Otherwise you get: $ make arch/x86/events/amd/ibs.s scripts/Makefile.build:44: arch/x86/events/amd/Makefile: No such file or directory make[1]: *** No rule to make target 'arch/x86/events/amd/Makefile'. Stop. Makefile:1636: recipe for target 'arch/x86/events/amd/ibs.s' failed make: *** [arch/x86/events/amd/ibs.s] Error 2Signed-off-by: Borislav Petkov Signed-off-by: Peter Zijlstra (Intel) Cc: Alexander Shishkin Cc: Arnaldo Carvalho de Melo Cc: Jiri Olsa Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Stephane Eranian Cc: Thomas Gleixner Cc: Vince Weaver Link: http://lkml.kernel.org/r/20170126080819.417-1-bp@alien8.deSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/events/amd/Makefile