mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-10-09 10:09:11 +00: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>
148 lines
4.5 KiB
Text
148 lines
4.5 KiB
Text
# SPDX-License-Identifier: GPL-2.0
|
|
#
|
|
# MN10300 CPU cache options
|
|
#
|
|
|
|
choice
|
|
prompt "CPU Caching mode"
|
|
default MN10300_CACHE_WBACK
|
|
help
|
|
This option determines the caching mode for the kernel.
|
|
|
|
Write-Back caching mode involves the all reads and writes causing
|
|
the affected cacheline to be read into the cache first before being
|
|
operated upon. Memory is not then updated by a write until the cache
|
|
is filled and a cacheline needs to be displaced from the cache to
|
|
make room. Only at that point is it written back.
|
|
|
|
Write-Through caching only fetches cachelines from memory on a
|
|
read. Writes always get written directly to memory. If the affected
|
|
cacheline is also in cache, it will be updated too.
|
|
|
|
The final option is to turn of caching entirely.
|
|
|
|
config MN10300_CACHE_WBACK
|
|
bool "Write-Back"
|
|
help
|
|
The dcache operates in delayed write-back mode. It must be manually
|
|
flushed if writes are made that subsequently need to be executed or
|
|
to be DMA'd by a device.
|
|
|
|
config MN10300_CACHE_WTHRU
|
|
bool "Write-Through"
|
|
help
|
|
The dcache operates in immediate write-through mode. Writes are
|
|
committed to RAM immediately in addition to being stored in the
|
|
cache. This means that the written data is immediately available for
|
|
execution or DMA.
|
|
|
|
This is not available for use with an SMP kernel if cache flushing
|
|
and invalidation by automatic purge register is not selected.
|
|
|
|
config MN10300_CACHE_DISABLED
|
|
bool "Disabled"
|
|
help
|
|
The icache and dcache are disabled.
|
|
|
|
endchoice
|
|
|
|
config MN10300_CACHE_ENABLED
|
|
def_bool y if !MN10300_CACHE_DISABLED
|
|
|
|
|
|
choice
|
|
prompt "CPU cache flush/invalidate method"
|
|
default MN10300_CACHE_MANAGE_BY_TAG if !AM34_2
|
|
default MN10300_CACHE_MANAGE_BY_REG if AM34_2
|
|
depends on MN10300_CACHE_ENABLED
|
|
help
|
|
This determines the method by which CPU cache flushing and
|
|
invalidation is performed.
|
|
|
|
config MN10300_CACHE_MANAGE_BY_TAG
|
|
bool "Use the cache tag registers directly"
|
|
depends on !(SMP && MN10300_CACHE_WTHRU)
|
|
|
|
config MN10300_CACHE_MANAGE_BY_REG
|
|
bool "Flush areas by way of automatic purge registers (AM34 only)"
|
|
depends on AM34_2
|
|
|
|
endchoice
|
|
|
|
config MN10300_CACHE_INV_BY_TAG
|
|
def_bool y if MN10300_CACHE_MANAGE_BY_TAG && MN10300_CACHE_ENABLED
|
|
|
|
config MN10300_CACHE_INV_BY_REG
|
|
def_bool y if MN10300_CACHE_MANAGE_BY_REG && MN10300_CACHE_ENABLED
|
|
|
|
config MN10300_CACHE_FLUSH_BY_TAG
|
|
def_bool y if MN10300_CACHE_MANAGE_BY_TAG && MN10300_CACHE_WBACK
|
|
|
|
config MN10300_CACHE_FLUSH_BY_REG
|
|
def_bool y if MN10300_CACHE_MANAGE_BY_REG && MN10300_CACHE_WBACK
|
|
|
|
|
|
config MN10300_HAS_CACHE_SNOOP
|
|
def_bool n
|
|
|
|
config MN10300_CACHE_SNOOP
|
|
bool "Use CPU Cache Snooping"
|
|
depends on MN10300_CACHE_ENABLED && MN10300_HAS_CACHE_SNOOP
|
|
default y
|
|
|
|
config MN10300_CACHE_FLUSH_ICACHE
|
|
def_bool y if MN10300_CACHE_WBACK && !MN10300_CACHE_SNOOP
|
|
help
|
|
Set if we need the dcache flushing before the icache is invalidated.
|
|
|
|
config MN10300_CACHE_INV_ICACHE
|
|
def_bool y if MN10300_CACHE_WTHRU && !MN10300_CACHE_SNOOP
|
|
help
|
|
Set if we need the icache to be invalidated, even if the dcache is in
|
|
write-through mode and doesn't need flushing.
|
|
|
|
#
|
|
# The kernel debugger gets its own separate cache flushing functions
|
|
#
|
|
config MN10300_DEBUGGER_CACHE_FLUSH_BY_TAG
|
|
def_bool y if KERNEL_DEBUGGER && \
|
|
MN10300_CACHE_WBACK && \
|
|
!MN10300_CACHE_SNOOP && \
|
|
MN10300_CACHE_MANAGE_BY_TAG
|
|
help
|
|
Set if the debugger needs to flush the dcache and invalidate the
|
|
icache using the cache tag registers to make breakpoints work.
|
|
|
|
config MN10300_DEBUGGER_CACHE_FLUSH_BY_REG
|
|
def_bool y if KERNEL_DEBUGGER && \
|
|
MN10300_CACHE_WBACK && \
|
|
!MN10300_CACHE_SNOOP && \
|
|
MN10300_CACHE_MANAGE_BY_REG
|
|
help
|
|
Set if the debugger needs to flush the dcache and invalidate the
|
|
icache using automatic purge registers to make breakpoints work.
|
|
|
|
config MN10300_DEBUGGER_CACHE_INV_BY_TAG
|
|
def_bool y if KERNEL_DEBUGGER && \
|
|
MN10300_CACHE_WTHRU && \
|
|
!MN10300_CACHE_SNOOP && \
|
|
MN10300_CACHE_MANAGE_BY_TAG
|
|
help
|
|
Set if the debugger needs to invalidate the icache using the cache
|
|
tag registers to make breakpoints work.
|
|
|
|
config MN10300_DEBUGGER_CACHE_INV_BY_REG
|
|
def_bool y if KERNEL_DEBUGGER && \
|
|
MN10300_CACHE_WTHRU && \
|
|
!MN10300_CACHE_SNOOP && \
|
|
MN10300_CACHE_MANAGE_BY_REG
|
|
help
|
|
Set if the debugger needs to invalidate the icache using automatic
|
|
purge registers to make breakpoints work.
|
|
|
|
config MN10300_DEBUGGER_CACHE_NO_FLUSH
|
|
def_bool y if KERNEL_DEBUGGER && \
|
|
(MN10300_CACHE_DISABLED || MN10300_CACHE_SNOOP)
|
|
help
|
|
Set if the debugger does not need to flush the dcache and/or
|
|
invalidate the icache to make breakpoints work.
|