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 22:07:57 +08:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
2017-06-01 00:59:30 +08:00
|
|
|
/*
|
|
|
|
|
* include/linux/arch_topology.h - arch specific cpu topology information
|
|
|
|
|
*/
|
|
|
|
|
#ifndef _LINUX_ARCH_TOPOLOGY_H_
|
|
|
|
|
#define _LINUX_ARCH_TOPOLOGY_H_
|
|
|
|
|
|
2017-06-23 17:25:32 +08:00
|
|
|
#include <linux/types.h>
|
2017-09-27 00:41:10 +08:00
|
|
|
#include <linux/percpu.h>
|
2017-06-23 17:25:32 +08:00
|
|
|
|
2017-06-01 00:59:31 +08:00
|
|
|
void topology_normalize_cpu_scale(void);
|
2018-07-20 21:32:32 +08:00
|
|
|
int topology_update_cpu_topology(void);
|
2017-06-01 00:59:30 +08:00
|
|
|
|
|
|
|
|
struct device_node;
|
2017-06-23 17:25:32 +08:00
|
|
|
bool topology_parse_cpu_capacity(struct device_node *cpu_node, int cpu);
|
2017-06-01 00:59:30 +08:00
|
|
|
|
2017-09-27 00:41:11 +08:00
|
|
|
DECLARE_PER_CPU(unsigned long, cpu_scale);
|
|
|
|
|
|
2020-02-12 02:15:15 +08:00
|
|
|
static inline unsigned long topology_get_cpu_scale(int cpu)
|
2017-09-27 00:41:11 +08:00
|
|
|
{
|
|
|
|
|
return per_cpu(cpu_scale, cpu);
|
|
|
|
|
}
|
2017-06-01 00:59:30 +08:00
|
|
|
|
2017-06-01 00:59:31 +08:00
|
|
|
void topology_set_cpu_scale(unsigned int cpu, unsigned long capacity);
|
2017-06-01 00:59:30 +08:00
|
|
|
|
2021-03-10 10:46:40 +08:00
|
|
|
DECLARE_PER_CPU(unsigned long, arch_freq_scale);
|
2017-09-27 00:41:10 +08:00
|
|
|
|
2020-02-12 02:15:15 +08:00
|
|
|
static inline unsigned long topology_get_freq_scale(int cpu)
|
2017-09-27 00:41:10 +08:00
|
|
|
{
|
2021-03-10 10:46:40 +08:00
|
|
|
return per_cpu(arch_freq_scale, cpu);
|
2017-09-27 00:41:10 +08:00
|
|
|
}
|
|
|
|
|
|
2020-09-24 20:30:15 +08:00
|
|
|
void topology_set_freq_scale(const struct cpumask *cpus, unsigned long cur_freq,
|
|
|
|
|
unsigned long max_freq);
|
arch_topology, arm, arm64: define arch_scale_freq_invariant()
arch_scale_freq_invariant() is used by schedutil to determine whether
the scheduler's load-tracking signals are frequency invariant. Its
definition is overridable, though by default it is hardcoded to 'true'
if arch_scale_freq_capacity() is defined ('false' otherwise).
This behaviour is not overridden on arm, arm64 and other users of the
generic arch topology driver, which is somewhat precarious:
arch_scale_freq_capacity() will always be defined, yet not all cpufreq
drivers are guaranteed to drive the frequency invariance scale factor
setting. In other words, the load-tracking signals may very well *not*
be frequency invariant.
Now that cpufreq can be queried on whether the current driver is driving
the Frequency Invariance (FI) scale setting, the current situation can
be improved. This combines the query of whether cpufreq supports the
setting of the frequency scale factor, with whether all online CPUs are
counter-based FI enabled.
While cpufreq FI enablement applies at system level, for all CPUs,
counter-based FI support could also be used for only a subset of CPUs to
set the invariance scale factor. Therefore, if cpufreq-based FI support
is present, we consider the system to be invariant. If missing, we
require all online CPUs to be counter-based FI enabled in order for the
full system to be considered invariant.
If the system ends up not being invariant, a new condition is needed in
the counter initialization code that disables all scale factor setting
based on counters.
Precedence of counters over cpufreq use is not important here. The
invariant status is only given to the system if all CPUs have at least
one method of setting the frequency scale factor.
Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
Signed-off-by: Ionela Voinescu <ionela.voinescu@arm.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2020-09-02 04:55:49 +08:00
|
|
|
bool topology_scale_freq_invariant(void);
|
|
|
|
|
|
2021-03-10 10:51:04 +08:00
|
|
|
enum scale_freq_source {
|
|
|
|
|
SCALE_FREQ_SOURCE_CPUFREQ = 0,
|
|
|
|
|
SCALE_FREQ_SOURCE_ARCH,
|
2020-06-23 18:19:40 +08:00
|
|
|
SCALE_FREQ_SOURCE_CPPC,
|
2021-03-10 10:51:04 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct scale_freq_data {
|
|
|
|
|
enum scale_freq_source source;
|
|
|
|
|
void (*set_freq_scale)(void);
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
void topology_scale_freq_tick(void);
|
|
|
|
|
void topology_set_scale_freq_source(struct scale_freq_data *data, const struct cpumask *cpus);
|
|
|
|
|
void topology_clear_scale_freq_source(enum scale_freq_source source, const struct cpumask *cpus);
|
arm64: use activity monitors for frequency invariance
The Frequency Invariance Engine (FIE) is providing a frequency
scaling correction factor that helps achieve more accurate
load-tracking.
So far, for arm and arm64 platforms, this scale factor has been
obtained based on the ratio between the current frequency and the
maximum supported frequency recorded by the cpufreq policy. The
setting of this scale factor is triggered from cpufreq drivers by
calling arch_set_freq_scale. The current frequency used in computation
is the frequency requested by a governor, but it may not be the
frequency that was implemented by the platform.
This correction factor can also be obtained using a core counter and a
constant counter to get information on the performance (frequency based
only) obtained in a period of time. This will more accurately reflect
the actual current frequency of the CPU, compared with the alternative
implementation that reflects the request of a performance level from
the OS.
Therefore, implement arch_scale_freq_tick to use activity monitors, if
present, for the computation of the frequency scale factor.
The use of AMU counters depends on:
- CONFIG_ARM64_AMU_EXTN - depents on the AMU extension being present
- CONFIG_CPU_FREQ - the current frequency obtained using counter
information is divided by the maximum frequency obtained from the
cpufreq policy.
While it is possible to have a combination of CPUs in the system with
and without support for activity monitors, the use of counters for
frequency invariance is only enabled for a CPU if all related CPUs
(CPUs in the same frequency domain) support and have enabled the core
and constant activity monitor counters. In this way, there is a clear
separation between the policies for which arch_set_freq_scale (cpufreq
based FIE) is used, and the policies for which arch_scale_freq_tick
(counter based FIE) is used to set the frequency scale factor. For
this purpose, a late_initcall_sync is registered to trigger validation
work for policies that will enable or disable the use of AMU counters
for frequency invariance. If CONFIG_CPU_FREQ is not defined, the use
of counters is enabled on all CPUs only if all possible CPUs correctly
support the necessary counters.
Signed-off-by: Ionela Voinescu <ionela.voinescu@arm.com>
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
Acked-by: Sudeep Holla <sudeep.holla@arm.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>
Cc: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2020-03-05 17:06:26 +08:00
|
|
|
|
2020-02-22 08:52:07 +08:00
|
|
|
DECLARE_PER_CPU(unsigned long, thermal_pressure);
|
|
|
|
|
|
|
|
|
|
static inline unsigned long topology_get_thermal_pressure(int cpu)
|
|
|
|
|
{
|
|
|
|
|
return per_cpu(thermal_pressure, cpu);
|
|
|
|
|
}
|
|
|
|
|
|
2020-07-13 00:59:15 +08:00
|
|
|
void topology_set_thermal_pressure(const struct cpumask *cpus,
|
|
|
|
|
unsigned long th_pressure);
|
2020-02-22 08:52:07 +08:00
|
|
|
|
2019-06-28 03:52:58 +08:00
|
|
|
struct cpu_topology {
|
|
|
|
|
int thread_id;
|
|
|
|
|
int core_id;
|
2021-09-24 16:51:02 +08:00
|
|
|
int cluster_id;
|
2019-06-28 03:52:58 +08:00
|
|
|
int package_id;
|
|
|
|
|
int llc_id;
|
|
|
|
|
cpumask_t thread_sibling;
|
|
|
|
|
cpumask_t core_sibling;
|
2021-09-24 16:51:02 +08:00
|
|
|
cpumask_t cluster_sibling;
|
2019-06-28 03:52:58 +08:00
|
|
|
cpumask_t llc_sibling;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#ifdef CONFIG_GENERIC_ARCH_TOPOLOGY
|
|
|
|
|
extern struct cpu_topology cpu_topology[NR_CPUS];
|
|
|
|
|
|
|
|
|
|
#define topology_physical_package_id(cpu) (cpu_topology[cpu].package_id)
|
2021-09-24 16:51:02 +08:00
|
|
|
#define topology_cluster_id(cpu) (cpu_topology[cpu].cluster_id)
|
2019-06-28 03:52:58 +08:00
|
|
|
#define topology_core_id(cpu) (cpu_topology[cpu].core_id)
|
|
|
|
|
#define topology_core_cpumask(cpu) (&cpu_topology[cpu].core_sibling)
|
|
|
|
|
#define topology_sibling_cpumask(cpu) (&cpu_topology[cpu].thread_sibling)
|
2021-09-24 16:51:02 +08:00
|
|
|
#define topology_cluster_cpumask(cpu) (&cpu_topology[cpu].cluster_sibling)
|
2019-06-28 03:52:58 +08:00
|
|
|
#define topology_llc_cpumask(cpu) (&cpu_topology[cpu].llc_sibling)
|
|
|
|
|
void init_cpu_topology(void);
|
|
|
|
|
void store_cpu_topology(unsigned int cpuid);
|
|
|
|
|
const struct cpumask *cpu_coregroup_mask(int cpu);
|
2021-09-24 16:51:02 +08:00
|
|
|
const struct cpumask *cpu_clustergroup_mask(int cpu);
|
2019-06-28 03:52:58 +08:00
|
|
|
void update_siblings_masks(unsigned int cpu);
|
|
|
|
|
void remove_cpu_topology(unsigned int cpuid);
|
2019-06-28 03:52:59 +08:00
|
|
|
void reset_cpu_topology(void);
|
2019-10-22 16:43:23 +08:00
|
|
|
int parse_acpi_topology(void);
|
2019-06-28 03:52:59 +08:00
|
|
|
#endif
|
2019-06-28 03:52:58 +08:00
|
|
|
|
2017-06-01 00:59:30 +08:00
|
|
|
#endif /* _LINUX_ARCH_TOPOLOGY_H_ */
|