Changes in runtime_instr.c

9eaba29c - s390/runtime_instrumentation: fix storage key handling

Wed, 12 Aug 2020 16:55:41 +0000

s390/runtime_instrumentation: fix storage key handlingThe key member of the runtime instrumentation control block containsonly the access key, not the complete storage key. Therefore the valuemust be shifted by four bits.Note: this is only relevant for debugging purposes in case somebodycompiles a kernel with a default storage access key set to a value notequal to zero.Fixes: e4b8b3f33fca ("s390: add support for runtime instrumentation")Reported-by: Claudio Imbrenda Signed-off-by: Heiko Carstens List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

65875530 - s390/runtime_instrumentation: re-add signum system call parameter

Sat, 27 Jan 2018 11:40:13 +0000

s390/runtime_instrumentation: re-add signum system call parameterAdd the signum system call parameter for documentation purposes only,and without checking if the passed value is a valid real-time signal.Signed-off-by: Heiko Carstens Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

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/s390/kernel/runtime_instr.c

bb59c2da - s390/runtime_instrumentation: clean up struct runtime_instr_cb

Thu, 14 Sep 2017 10:35:45 +0000

s390/runtime_instrumentation: clean up struct runtime_instr_cbUpdate runtime_instr_cb structure to be consistent with the runtimeinstrumentation documentation.Signed-off-by: Alice Frosi Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

8d9047f8 - s390/runtime instrumentation: simplify task exit handling

Mon, 11 Sep 2017 09:24:22 +0000

s390/runtime instrumentation: simplify task exit handlingFree data structures required for runtime instrumentation fromarch_release_task_struct(). This allows to simplify the code a bit,and also makes the semantics a bit easier: arch_release_task_struct()is never called from the task that is being removed.In addition this allows to get rid of exit_thread() in a later patch.Signed-off-by: Heiko Carstens Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

d6e646ad - s390/runtime instrumention: fix possible memory corruption

Mon, 11 Sep 2017 09:24:22 +0000

s390/runtime instrumention: fix possible memory corruptionFor PREEMPT enabled kernels the runtime instrumentation (RI) codecontains a possible use-after-free bug. If a task that makes use of RIexits, it will execute do_exit() while still enabled for preemption.That function will call exit_thread_runtime_instr() viaexit_thread(). If exit_thread_runtime_instr() gets preempted after theRI control block of the task has been freed but before the pointer toit is set to NULL, then save_ri_cb(), called from switch_to(), willwrite to already freed memory.Avoid this and simply disable preemption while freeing the controlblock and setting the pointer to NULL.Fixes: e4b8b3f33fca ("s390: add support for runtime instrumentation")Cc: # v3.7+Reviewed-by: Christian Borntraeger Signed-off-by: Heiko Carstens Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

68db0cf1 - sched/headers: Prepare for new header dependencies before moving code to

Wed, 08 Feb 2017 17:51:37 +0000

sched/headers: Prepare for new header dependencies before moving code to We are going to split out of , whichwill have to be picked up from other headers and a couple of .c files.Create a trivial placeholder file that justmaps to to make this patch obviously correct andbisectable.Include the new header in the files that are going to need it.Acked-by: Linus Torvalds Cc: Mike Galbraith Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: linux-kernel@vger.kernel.orgSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

b38feccd - s390: remove runtime instrumentation interrupts

Mon, 02 Nov 2015 13:03:46 +0000

s390: remove runtime instrumentation interruptsThe external interrupts for runtime instrumentation buffer-fulland runtime instrumentation halted are unused and have no currentuser. Remove the support and ignore the second parameter of thes390_runtime_instr system call from now on.Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

1dad093b - s390/irq: Use defines for external interruption codes

Mon, 31 Mar 2014 13:24:08 +0000

s390/irq: Use defines for external interruption codesUse the new defines for external interruption codes to get ridof "magic" numbers in the s390 source code. And while we're at it,also rename the (un-)register_external_interrupt function tosomething shorter so that this patch does not exceed the 80columns all over the place.Signed-off-by: Thomas Huth Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

e258d719 - s390/uaccess: always run the kernel in home space

Tue, 24 Sep 2013 07:14:56 +0000

s390/uaccess: always run the kernel in home spaceSimplify the uaccess code by removing the user_mode=home option.The kernel will now always run in the home space mode.Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

82003c3e - s390/irq: rework irq subclass handling

Wed, 04 Sep 2013 11:35:45 +0000

s390/irq: rework irq subclass handlingLet's not add a function for every external interrupt subclass forwhich we need reference counting. Just have two register/unregisterfunctions which have a subclass parameter:void irq_subclass_register(enum irq_subclass subclass);void irq_subclass_unregister(enum irq_subclass subclass);Signed-off-by: Heiko Carstens List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

420f42ec - s390/irq: remove split irq fields from /proc/stat

Wed, 02 Jan 2013 14:18:18 +0000

s390/irq: remove split irq fields from /proc/statNow that irq sum accounting for /proc/stat's "intr" line works again wehave the oddity that the sum field (first field) contains only the sumof the second (external irqs) and third field (I/O interrupts).The reason for that is that these two fields are already sums of all otherfields. So if we would sum up everything we would count every interrupttwice.This is broken since the split interrupt accounting was merged two yearsago: 052ff461c8427629aee887ccc27478fc7373237c "[S390] irq: have detailedstatistics for interrupt types".To fix this remove the split interrupt fields from /proc/stat's "intr"line again and only have them in /proc/interrupts.This restores the old behaviour, seems to be the only sane fix and mimicsa behaviour from other architectures where /proc/interrupts also containsmore than /proc/stat's "intr" line does.Signed-off-by: Heiko Carstens Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

d1b0d842 - s390/mm: rename addressing_mode to s390_user_mode

Sun, 02 Sep 2012 09:02:23 +0000

s390/mm: rename addressing_mode to s390_user_modeRenaming the globally visible variable "user_mode" to "addressing_mode" inorder to fix a name clash was not a good idea. (Commit 37fe1d73 "s390/mm:rename user_mode variable to addressing_mode")Looking at the code after a couple of weeks one thinks: addressing mode ofwhat?So rename the variable again. This time to s390_user_mode. Which hopefullymakes more sense.Signed-off-by: Heiko Carstens Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c

e4b8b3f3 - s390: add support for runtime instrumentation

Tue, 31 Jul 2012 08:52:05 +0000

s390: add support for runtime instrumentationAllow user-space threads to use runtime instrumentation (RI). To enable RIfor a thread there is a new s390 specific system call, sys_s390_runtime_instr,that takes as parameter a realtime signal number. If the RI facility isavailable the system call sets up a control block for the calling thread withthe appropriate permissions for the thread to modify the control block.The user-space thread can then use the store and modify RI instructions toalter the control block and start/stop the instrumentation via RION/RIOFF.If the user specified program buffer runs full RI triggers an externalinterrupt. The external interrupt is translated to a real-time signal thatis delivered to the thread that enabled RI on that CPU. The number ofthe real-time signal is the number specified in the RI system call. So,user-space can select any available real-time signal number in case theapplication itself uses real-time signals for other purposes.The kernel saves the RI control blocks on task switch only if the runningthread was enabled for RI. Therefore, the performance impact on task switchshould be negligible if RI is not used.RI is only enabled for user-space mode and is disabled for the supervisorstate.Reviewed-by: Heiko Carstens Signed-off-by: Jan Glauber Signed-off-by: Martin Schwidefsky List of files: /linux-6.15/arch/s390/kernel/runtime_instr.c