License cleanup: add SPDX GPL-2.0 license identifier to files with no license
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>
2017-11-01 07:07:57 -07:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2006-01-16 23:14:19 -07:00
|
|
|
menu "Memory management options"
|
|
|
|
|
|
|
|
|
|
config MMU
|
|
|
|
|
bool "Support for memory management hardware"
|
|
|
|
|
depends on !CPU_SH2
|
2024-02-23 15:18:37 -07:00
|
|
|
select HAVE_PAGE_SIZE_4KB
|
|
|
|
|
select HAVE_PAGE_SIZE_8KB if X2TLB
|
|
|
|
|
select HAVE_PAGE_SIZE_64KB if CPU_SH4
|
2006-01-16 23:14:19 -07:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Some SH processors (such as SH-2/SH-2A) lack an MMU. In order to
|
|
|
|
|
boot on these systems, this option must not be set.
|
|
|
|
|
|
|
|
|
|
On other systems (such as the SH-3 and 4) where an MMU exists,
|
|
|
|
|
turning this off will boot the kernel on these machines with the
|
|
|
|
|
MMU implicitly switched off.
|
|
|
|
|
|
2024-02-23 15:18:37 -07:00
|
|
|
config NOMMU
|
|
|
|
|
def_bool !MMU
|
|
|
|
|
select HAVE_PAGE_SIZE_4KB
|
|
|
|
|
select HAVE_PAGE_SIZE_8KB
|
|
|
|
|
select HAVE_PAGE_SIZE_16KB
|
|
|
|
|
select HAVE_PAGE_SIZE_64KB
|
|
|
|
|
help
|
|
|
|
|
On MMU-less systems, any of these page sizes can be selected
|
|
|
|
|
|
2006-09-27 01:19:13 -07:00
|
|
|
config PAGE_OFFSET
|
|
|
|
|
hex
|
2020-04-20 02:37:12 -07:00
|
|
|
default "0x80000000" if MMU
|
2006-09-27 01:19:13 -07:00
|
|
|
default "0x00000000"
|
|
|
|
|
|
2022-08-15 07:39:59 -07:00
|
|
|
config ARCH_FORCE_MAX_ORDER
|
2023-03-23 22:22:30 -07:00
|
|
|
int "Order of maximal physically contiguous allocations"
|
2023-03-15 04:31:33 -07:00
|
|
|
default "8" if PAGE_SIZE_16KB
|
|
|
|
|
default "6" if PAGE_SIZE_64KB
|
|
|
|
|
default "13" if !MMU
|
|
|
|
|
default "10"
|
2009-05-14 01:40:08 -07:00
|
|
|
help
|
2023-03-23 22:22:30 -07:00
|
|
|
The kernel page allocator limits the size of maximal physically
|
2023-12-28 07:47:04 -07:00
|
|
|
contiguous allocations. The limit is called MAX_PAGE:_ORDER and it
|
2023-03-23 22:22:30 -07:00
|
|
|
defines the maximal power of two of number of pages that can be
|
|
|
|
|
allocated as a single contiguous block. This option allows
|
|
|
|
|
overriding the default setting when ability to allocate very
|
|
|
|
|
large blocks of physically contiguous memory is required.
|
2009-05-14 01:40:08 -07:00
|
|
|
|
|
|
|
|
The page size is not necessarily 4KB. Keep this in mind when
|
|
|
|
|
choosing a value for this option.
|
|
|
|
|
|
2023-03-23 22:22:30 -07:00
|
|
|
Don't change if unsure.
|
|
|
|
|
|
2006-09-27 01:19:13 -07:00
|
|
|
config MEMORY_START
|
|
|
|
|
hex "Physical memory start address"
|
|
|
|
|
default "0x08000000"
|
2020-06-13 09:50:22 -07:00
|
|
|
help
|
2006-09-27 01:19:13 -07:00
|
|
|
Computers built with Hitachi SuperH processors always
|
|
|
|
|
map the ROM starting at address zero. But the processor
|
|
|
|
|
does not specify the range that RAM takes.
|
|
|
|
|
|
|
|
|
|
The physical memory (RAM) start address will be automatically
|
|
|
|
|
set to 08000000. Other platforms, such as the Solution Engine
|
|
|
|
|
boards typically map RAM at 0C000000.
|
|
|
|
|
|
|
|
|
|
Tweak this only when porting to a new machine which does not
|
|
|
|
|
already have a defconfig. Changing it from the known correct
|
|
|
|
|
value on any of the known systems will only lead to disaster.
|
|
|
|
|
|
|
|
|
|
config MEMORY_SIZE
|
|
|
|
|
hex "Physical memory size"
|
2007-11-20 23:46:07 -07:00
|
|
|
default "0x04000000"
|
2006-09-27 01:19:13 -07:00
|
|
|
help
|
|
|
|
|
This sets the default memory size assumed by your SH kernel. It can
|
|
|
|
|
be overridden as normal by the 'mem=' argument on the kernel command
|
|
|
|
|
line. If unsure, consult your board specifications or just leave it
|
2007-11-20 23:46:07 -07:00
|
|
|
as 0x04000000 which was the default value before this became
|
2006-09-27 01:19:13 -07:00
|
|
|
configurable.
|
|
|
|
|
|
2007-11-10 03:16:55 -07:00
|
|
|
# Physical addressing modes
|
|
|
|
|
|
|
|
|
|
config 29BIT
|
|
|
|
|
def_bool !32BIT
|
2010-02-11 23:40:00 -07:00
|
|
|
select UNCACHED_MAPPING
|
2007-11-10 03:16:55 -07:00
|
|
|
|
2006-01-16 23:14:19 -07:00
|
|
|
config 32BIT
|
2007-11-10 03:16:55 -07:00
|
|
|
bool
|
2020-04-20 02:37:12 -07:00
|
|
|
default !MMU
|
2007-11-10 03:16:55 -07:00
|
|
|
|
2009-03-09 23:49:54 -07:00
|
|
|
config PMB
|
2010-01-13 02:31:48 -07:00
|
|
|
bool "Support 32-bit physical addressing through PMB"
|
2013-01-16 19:53:26 -07:00
|
|
|
depends on MMU && CPU_SH4A && !CPU_SH4AL_DSP
|
2010-01-13 02:31:48 -07:00
|
|
|
select 32BIT
|
2010-02-11 23:40:00 -07:00
|
|
|
select UNCACHED_MAPPING
|
2009-03-09 23:49:54 -07:00
|
|
|
help
|
|
|
|
|
If you say Y here, physical addressing will be extended to
|
|
|
|
|
32-bits through the SH-4A PMB. If this is not set, legacy
|
|
|
|
|
29-bit physical addressing will be used.
|
|
|
|
|
|
2006-11-19 22:30:26 -07:00
|
|
|
config X2TLB
|
2010-01-13 03:11:14 -07:00
|
|
|
def_bool y
|
|
|
|
|
depends on (CPU_SHX2 || CPU_SHX3) && MMU
|
2006-11-19 22:30:26 -07:00
|
|
|
|
2006-09-27 02:33:49 -07:00
|
|
|
config VSYSCALL
|
|
|
|
|
bool "Support vsyscall page"
|
2007-11-08 02:54:16 -07:00
|
|
|
depends on MMU && (CPU_SH3 || CPU_SH4)
|
2006-09-27 02:33:49 -07:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This will enable support for the kernel mapping a vDSO page
|
|
|
|
|
in process space, and subsequently handing down the entry point
|
|
|
|
|
to the libc through the ELF auxiliary vector.
|
|
|
|
|
|
|
|
|
|
From the kernel side this is used for the signal trampoline.
|
|
|
|
|
For systems with an MMU that can afford to give up a page,
|
|
|
|
|
(the default value) say Y.
|
|
|
|
|
|
2007-06-06 01:52:19 -07:00
|
|
|
config NUMA
|
2020-09-17 19:14:04 -07:00
|
|
|
bool "Non-Uniform Memory Access (NUMA) Support"
|
2013-01-16 19:53:26 -07:00
|
|
|
depends on MMU && SYS_SUPPORTS_NUMA
|
2012-10-25 05:16:43 -07:00
|
|
|
select ARCH_WANT_NUMA_VARIABLE_LOCALITY
|
2007-06-06 01:52:19 -07:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Some SH systems have many various memories scattered around
|
|
|
|
|
the address space, each with varying latencies. This enables
|
|
|
|
|
support for these blocks by binding them to nodes and allowing
|
|
|
|
|
memory policies to be used for prioritizing and controlling
|
|
|
|
|
allocation behaviour.
|
|
|
|
|
|
2007-03-28 00:38:13 -07:00
|
|
|
config NODES_SHIFT
|
|
|
|
|
int
|
2007-08-08 00:45:07 -07:00
|
|
|
default "3" if CPU_SUBTYPE_SHX3
|
2007-03-28 00:38:13 -07:00
|
|
|
default "1"
|
2021-06-28 19:43:01 -07:00
|
|
|
depends on NUMA
|
2007-03-28 00:38:13 -07:00
|
|
|
|
|
|
|
|
config ARCH_FLATMEM_ENABLE
|
|
|
|
|
def_bool y
|
2007-06-10 23:32:07 -07:00
|
|
|
depends on !NUMA
|
2007-03-28 00:38:13 -07:00
|
|
|
|
2007-05-23 01:48:36 -07:00
|
|
|
config ARCH_SPARSEMEM_ENABLE
|
|
|
|
|
def_bool y
|
|
|
|
|
select SPARSEMEM_STATIC
|
|
|
|
|
|
|
|
|
|
config ARCH_SPARSEMEM_DEFAULT
|
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
|
|
config ARCH_SELECT_MEMORY_MODEL
|
|
|
|
|
def_bool y
|
|
|
|
|
|
2009-11-05 00:54:17 -07:00
|
|
|
config IOREMAP_FIXED
|
|
|
|
|
def_bool y
|
2020-04-20 02:37:12 -07:00
|
|
|
depends on X2TLB
|
2009-11-05 00:54:17 -07:00
|
|
|
|
2010-02-11 23:40:00 -07:00
|
|
|
config UNCACHED_MAPPING
|
|
|
|
|
bool
|
|
|
|
|
|
2010-10-14 10:09:00 -07:00
|
|
|
config HAVE_SRAM_POOL
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_ALLOCATOR
|
|
|
|
|
|
2006-01-16 23:14:19 -07:00
|
|
|
choice
|
|
|
|
|
prompt "HugeTLB page size"
|
2009-10-26 15:22:37 -07:00
|
|
|
depends on HUGETLB_PAGE
|
2008-08-05 23:10:49 -07:00
|
|
|
default HUGETLB_PAGE_SIZE_1MB if PAGE_SIZE_64KB
|
2006-01-16 23:14:19 -07:00
|
|
|
default HUGETLB_PAGE_SIZE_64K
|
|
|
|
|
|
|
|
|
|
config HUGETLB_PAGE_SIZE_64K
|
2006-11-19 22:30:26 -07:00
|
|
|
bool "64kB"
|
2008-08-05 23:10:49 -07:00
|
|
|
depends on !PAGE_SIZE_64KB
|
2006-11-19 22:30:26 -07:00
|
|
|
|
|
|
|
|
config HUGETLB_PAGE_SIZE_256K
|
|
|
|
|
bool "256kB"
|
|
|
|
|
depends on X2TLB
|
2006-01-16 23:14:19 -07:00
|
|
|
|
|
|
|
|
config HUGETLB_PAGE_SIZE_1MB
|
|
|
|
|
bool "1MB"
|
|
|
|
|
|
2006-11-19 22:30:26 -07:00
|
|
|
config HUGETLB_PAGE_SIZE_4MB
|
|
|
|
|
bool "4MB"
|
|
|
|
|
depends on X2TLB
|
|
|
|
|
|
|
|
|
|
config HUGETLB_PAGE_SIZE_64MB
|
|
|
|
|
bool "64MB"
|
|
|
|
|
depends on X2TLB
|
|
|
|
|
|
2006-01-16 23:14:19 -07:00
|
|
|
endchoice
|
|
|
|
|
|
2009-10-16 02:00:02 -07:00
|
|
|
config SCHED_MC
|
|
|
|
|
bool "Multi-core scheduler support"
|
|
|
|
|
depends on SMP
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Multi-core scheduler support improves the CPU scheduler's decision
|
|
|
|
|
making when dealing with multi-core CPU chips at a cost of slightly
|
|
|
|
|
increased overhead in some places. If unsure say N here.
|
|
|
|
|
|
2006-01-16 23:14:19 -07:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
menu "Cache configuration"
|
|
|
|
|
|
|
|
|
|
config SH7705_CACHE_32KB
|
|
|
|
|
bool "Enable 32KB cache size for SH7705"
|
|
|
|
|
depends on CPU_SUBTYPE_SH7705
|
|
|
|
|
default y
|
|
|
|
|
|
2007-07-31 01:07:28 -07:00
|
|
|
choice
|
|
|
|
|
prompt "Cache mode"
|
2020-04-20 02:37:12 -07:00
|
|
|
default CACHE_WRITEBACK if CPU_SH2A || CPU_SH3 || CPU_SH4
|
2007-07-31 01:07:28 -07:00
|
|
|
default CACHE_WRITETHROUGH if (CPU_SH2 && !CPU_SH2A)
|
|
|
|
|
|
|
|
|
|
config CACHE_WRITEBACK
|
|
|
|
|
bool "Write-back"
|
|
|
|
|
|
|
|
|
|
config CACHE_WRITETHROUGH
|
|
|
|
|
bool "Write-through"
|
2006-01-16 23:14:19 -07:00
|
|
|
help
|
|
|
|
|
Selecting this option will configure the caches in write-through
|
|
|
|
|
mode, as opposed to the default write-back configuration.
|
|
|
|
|
|
|
|
|
|
Since there's sill some aliasing issues on SH-4, this option will
|
|
|
|
|
unfortunately still require the majority of flushing functions to
|
|
|
|
|
be implemented to deal with aliasing.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-07-31 01:07:28 -07:00
|
|
|
config CACHE_OFF
|
|
|
|
|
bool "Off"
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2006-01-16 23:14:19 -07:00
|
|
|
endmenu
|