mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-02 07:26:40 +07:00
b24413180f
Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license 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 binding shorthand, which can be used instead of the full boiler plate text. This patch is based on work done by Thomas Gleixner and Kate Stewart and Philippe Ombredanne. How this work was done: Patches were generated and checked against linux-4.14-rc6 for a subset of the 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 cases where non-standard license headers were used, and references to license had to be inferred by heuristics based on keywords. The analysis to determine which SPDX License Identifier to be applied to a file was done in a spreadsheet of side by side results from of the output of two independent scanners (ScanCode & Windriver) producing SPDX tag:value files created by Philippe Ombredanne. Philippe prepared the base 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 files assessed. Kate Stewart did a file by file comparison of the scanner results in the spreadsheet to determine which SPDX license identifier(s) to be applied to the file. She confirmed any determination that was not immediately 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 license identifiers 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 the spreadsheet to determine the SPDX license identifiers to apply to the source files by Kate, Philippe, Thomas and, in some cases, confirmation by lawyers working with the Linux Foundation. Kate also obtained a third independent scan of the 4.13 code base from FOSSology, and compared selected files where the other two scanners disagreed against that SPDX file, to see if there was new insights. The Windriver scanner is based on an older version of FOSSology in part, so they are related. Thomas did random spot checks in about 500 files from the spreadsheets for the uapi headers and agreed with SPDX license identifier in the files he inspected. For the non-uapi files Thomas did random spot checks in about 15000 files. In initial set of patches against 4.14-rc6, 3 files were found to have copy/paste license identifier errors, and have been fixed to reflect the correct identifier. Additionally Philippe spent 10 hours this week doing a detailed manual inspection and review of the 12,461 patched files from the initial patch version 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 correct This produced a worksheet with 20 files needing minor correction. This worksheet was then exported into 3 different .csv files for the different types of files to be modified. These .csv files were then reviewed by Greg. Thomas wrote a script to parse the csv files and add the proper SPDX tag to the file, in the format that the file expected. This script was further refined by Greg based on the output to detect more types of files automatically and to distinguish between header and source .c files (which need different comment types.) Finally Greg ran the script using the .csv files to generate the patches. Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org> Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com> Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
108 lines
2.7 KiB
C
108 lines
2.7 KiB
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
/*
|
|
* ARM KGDB support
|
|
*
|
|
* Author: Deepak Saxena <dsaxena@mvista.com>
|
|
*
|
|
* Copyright (C) 2002 MontaVista Software Inc.
|
|
*
|
|
*/
|
|
|
|
#ifndef __ARM_KGDB_H__
|
|
#define __ARM_KGDB_H__
|
|
|
|
#include <linux/ptrace.h>
|
|
#include <asm/opcodes.h>
|
|
|
|
/*
|
|
* GDB assumes that we're a user process being debugged, so
|
|
* it will send us an SWI command to write into memory as the
|
|
* debug trap. When an SWI occurs, the next instruction addr is
|
|
* placed into R14_svc before jumping to the vector trap.
|
|
* This doesn't work for kernel debugging as we are already in SVC
|
|
* we would loose the kernel's LR, which is a bad thing. This
|
|
* is bad thing.
|
|
*
|
|
* By doing this as an undefined instruction trap, we force a mode
|
|
* switch from SVC to UND mode, allowing us to save full kernel state.
|
|
*
|
|
* We also define a KGDB_COMPILED_BREAK which can be used to compile
|
|
* in breakpoints. This is important for things like sysrq-G and for
|
|
* the initial breakpoint from trap_init().
|
|
*
|
|
* Note to ARM HW designers: Add real trap support like SH && PPC to
|
|
* make our lives much much simpler. :)
|
|
*/
|
|
#define BREAK_INSTR_SIZE 4
|
|
#define GDB_BREAKINST 0xef9f0001
|
|
#define KGDB_BREAKINST 0xe7ffdefe
|
|
#define KGDB_COMPILED_BREAK 0xe7ffdeff
|
|
#define CACHE_FLUSH_IS_SAFE 1
|
|
|
|
#ifndef __ASSEMBLY__
|
|
|
|
static inline void arch_kgdb_breakpoint(void)
|
|
{
|
|
asm(__inst_arm(0xe7ffdeff));
|
|
}
|
|
|
|
extern void kgdb_handle_bus_error(void);
|
|
extern int kgdb_fault_expected;
|
|
|
|
#endif /* !__ASSEMBLY__ */
|
|
|
|
/*
|
|
* From Kevin Hilman:
|
|
*
|
|
* gdb is expecting the following registers layout.
|
|
*
|
|
* r0-r15: 1 long word each
|
|
* f0-f7: unused, 3 long words each !!
|
|
* fps: unused, 1 long word
|
|
* cpsr: 1 long word
|
|
*
|
|
* Even though f0-f7 and fps are not used, they need to be
|
|
* present in the registers sent for correct processing in
|
|
* the host-side gdb.
|
|
*
|
|
* In particular, it is crucial that CPSR is in the right place,
|
|
* otherwise gdb will not be able to correctly interpret stepping over
|
|
* conditional branches.
|
|
*/
|
|
#define _GP_REGS 16
|
|
#define _FP_REGS 8
|
|
#define _EXTRA_REGS 2
|
|
#define GDB_MAX_REGS (_GP_REGS + (_FP_REGS * 3) + _EXTRA_REGS)
|
|
#define DBG_MAX_REG_NUM (_GP_REGS + _FP_REGS + _EXTRA_REGS)
|
|
|
|
#define KGDB_MAX_NO_CPUS 1
|
|
#define BUFMAX 400
|
|
#define NUMREGBYTES (DBG_MAX_REG_NUM << 2)
|
|
#define NUMCRITREGBYTES (32 << 2)
|
|
|
|
#define _R0 0
|
|
#define _R1 1
|
|
#define _R2 2
|
|
#define _R3 3
|
|
#define _R4 4
|
|
#define _R5 5
|
|
#define _R6 6
|
|
#define _R7 7
|
|
#define _R8 8
|
|
#define _R9 9
|
|
#define _R10 10
|
|
#define _FP 11
|
|
#define _IP 12
|
|
#define _SPT 13
|
|
#define _LR 14
|
|
#define _PC 15
|
|
#define _CPSR (GDB_MAX_REGS - 1)
|
|
|
|
/*
|
|
* So that we can denote the end of a frame for tracing,
|
|
* in the simple case:
|
|
*/
|
|
#define CFI_END_FRAME(func) __CFI_END_FRAME(_PC, _SPT, func)
|
|
|
|
#endif /* __ASM_KGDB_H__ */
|