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 21:07:57 +07:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0 */
|
2014-03-14 12:00:38 +07:00
|
|
|
#ifndef LINUX_POWERPC_PERF_HV_24X7_H_
|
|
|
|
#define LINUX_POWERPC_PERF_HV_24X7_H_
|
|
|
|
|
|
|
|
#include <linux/types.h>
|
|
|
|
|
powerpc/perf/hv-24x7: parse catalog and populate sysfs with events
Retrieves and parses the 24x7 catalog on POWER systems that supply it
(right now, only POWER 8). Events are exposed via sysfs in the standard
fashion, and are all parameterized.
$ cd /sys/bus/event_source/devices/hv_24x7/events
$ cat HPM_CS_FROM_L4_LDATA__PHYS_CORE
domain=0x2,offset=0xd58,core=?,lpar=0x0
$ cat HPM_TLBIE__VCPU_HOME_CHIP
domain=0x4,offset=0x358,vcpu=?,lpar=?
where user is required to specify values for the fields with '?' (like
core, vcpu, lpar above), when specifying the event with the perf tool.
Catalog is (at the moment) only parsed on boot. It needs re-parsing
when a some hypervisor events occur. At that point we'll also need to
prevent old events from continuing to function (counter that is passed
in via spare space in the config values?).
Signed-off-by: Cody P Schafer <cody@linux.vnet.ibm.com>
Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
2015-01-31 04:46:00 +07:00
|
|
|
enum hv_perf_domains {
|
|
|
|
#define DOMAIN(n, v, x, c) HV_PERF_DOMAIN_##n = v,
|
|
|
|
#include "hv-24x7-domains.h"
|
|
|
|
#undef DOMAIN
|
2016-02-17 08:07:51 +07:00
|
|
|
HV_PERF_DOMAIN_MAX,
|
powerpc/perf/hv-24x7: parse catalog and populate sysfs with events
Retrieves and parses the 24x7 catalog on POWER systems that supply it
(right now, only POWER 8). Events are exposed via sysfs in the standard
fashion, and are all parameterized.
$ cd /sys/bus/event_source/devices/hv_24x7/events
$ cat HPM_CS_FROM_L4_LDATA__PHYS_CORE
domain=0x2,offset=0xd58,core=?,lpar=0x0
$ cat HPM_TLBIE__VCPU_HOME_CHIP
domain=0x4,offset=0x358,vcpu=?,lpar=?
where user is required to specify values for the fields with '?' (like
core, vcpu, lpar above), when specifying the event with the perf tool.
Catalog is (at the moment) only parsed on boot. It needs re-parsing
when a some hypervisor events occur. At that point we'll also need to
prevent old events from continuing to function (counter that is passed
in via spare space in the config values?).
Signed-off-by: Cody P Schafer <cody@linux.vnet.ibm.com>
Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
2015-01-31 04:46:00 +07:00
|
|
|
};
|
|
|
|
|
2017-06-30 04:55:37 +07:00
|
|
|
#define H24x7_REQUEST_SIZE(iface_version) (iface_version == 1 ? 16 : 32)
|
|
|
|
|
2014-03-14 12:00:38 +07:00
|
|
|
struct hv_24x7_request {
|
|
|
|
/* PHYSICAL domains require enabling via phyp/hmc. */
|
|
|
|
__u8 performance_domain;
|
|
|
|
__u8 reserved[0x1];
|
|
|
|
|
|
|
|
/* bytes to read starting at @data_offset. must be a multiple of 8 */
|
|
|
|
__be16 data_size;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* byte offset within the perf domain to read from. must be 8 byte
|
|
|
|
* aligned
|
|
|
|
*/
|
|
|
|
__be32 data_offset;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* only valid for VIRTUAL_PROCESSOR domains, ignored for others.
|
|
|
|
* -1 means "current partition only"
|
|
|
|
* Enabling via phyp/hmc required for non-"-1" values. 0 forbidden
|
|
|
|
* unless requestor is 0.
|
|
|
|
*/
|
|
|
|
__be16 starting_lpar_ix;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Ignored when @starting_lpar_ix == -1
|
|
|
|
* Ignored when @performance_domain is not VIRTUAL_PROCESSOR_*
|
|
|
|
* -1 means "infinite" or all
|
|
|
|
*/
|
|
|
|
__be16 max_num_lpars;
|
|
|
|
|
|
|
|
/* chip, core, or virtual processor based on @performance_domain */
|
|
|
|
__be16 starting_ix;
|
|
|
|
__be16 max_ix;
|
2017-06-30 04:55:37 +07:00
|
|
|
|
|
|
|
/* The following fields were added in v2 of the 24x7 interface. */
|
|
|
|
|
|
|
|
__u8 starting_thread_group_ix;
|
|
|
|
|
|
|
|
/* -1 means all thread groups starting at @starting_thread_group_ix */
|
|
|
|
__u8 max_num_thread_groups;
|
|
|
|
|
|
|
|
__u8 reserved2[0xE];
|
2014-03-14 12:00:38 +07:00
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct hv_24x7_request_buffer {
|
|
|
|
/* 0 - ? */
|
|
|
|
/* 1 - ? */
|
|
|
|
__u8 interface_version;
|
|
|
|
__u8 num_requests;
|
|
|
|
__u8 reserved[0xE];
|
2017-06-30 04:55:37 +07:00
|
|
|
struct hv_24x7_request requests[];
|
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct hv_24x7_result_element_v1 {
|
|
|
|
__be16 lpar_ix;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* represents the core, chip, or virtual processor based on the
|
|
|
|
* request's @performance_domain
|
|
|
|
*/
|
|
|
|
__be16 domain_ix;
|
|
|
|
|
|
|
|
/* -1 if @performance_domain does not refer to a virtual processor */
|
|
|
|
__be32 lpar_cfg_instance_id;
|
|
|
|
|
|
|
|
/* size = @result_element_data_size of containing result. */
|
|
|
|
__u64 element_data[];
|
2014-03-14 12:00:38 +07:00
|
|
|
} __packed;
|
|
|
|
|
2017-06-30 04:55:37 +07:00
|
|
|
/*
|
|
|
|
* We need a separate struct for v2 because the offset of @element_data changed
|
|
|
|
* between versions.
|
|
|
|
*/
|
|
|
|
struct hv_24x7_result_element_v2 {
|
2014-03-14 12:00:38 +07:00
|
|
|
__be16 lpar_ix;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* represents the core, chip, or virtual processor based on the
|
|
|
|
* request's @performance_domain
|
|
|
|
*/
|
|
|
|
__be16 domain_ix;
|
|
|
|
|
|
|
|
/* -1 if @performance_domain does not refer to a virtual processor */
|
|
|
|
__be32 lpar_cfg_instance_id;
|
|
|
|
|
2017-06-30 04:55:37 +07:00
|
|
|
__u8 thread_group_ix;
|
|
|
|
|
|
|
|
__u8 reserved[7];
|
|
|
|
|
2016-06-01 13:34:37 +07:00
|
|
|
/* size = @result_element_data_size of containing result. */
|
2017-06-30 04:55:37 +07:00
|
|
|
__u64 element_data[];
|
2014-03-14 12:00:38 +07:00
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct hv_24x7_result {
|
2017-06-30 04:55:36 +07:00
|
|
|
/*
|
|
|
|
* The index of the 24x7 Request Structure in the 24x7 Request Buffer
|
|
|
|
* used to request this result.
|
|
|
|
*/
|
2014-03-14 12:00:38 +07:00
|
|
|
__u8 result_ix;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 0 = not all result elements fit into the buffer, additional requests
|
|
|
|
* required
|
|
|
|
* 1 = all result elements were returned
|
|
|
|
*/
|
|
|
|
__u8 results_complete;
|
|
|
|
__be16 num_elements_returned;
|
|
|
|
|
2017-06-30 04:55:36 +07:00
|
|
|
/*
|
|
|
|
* This is a copy of @data_size from the corresponding hv_24x7_request
|
|
|
|
*
|
|
|
|
* Warning: to obtain the size of each element in @elements you have
|
|
|
|
* to add the size of the other members of the result_element struct.
|
|
|
|
*/
|
2014-03-14 12:00:38 +07:00
|
|
|
__be16 result_element_data_size;
|
|
|
|
__u8 reserved[0x2];
|
|
|
|
|
2017-06-30 04:55:37 +07:00
|
|
|
/*
|
|
|
|
* Either
|
|
|
|
* struct hv_24x7_result_element_v1[@num_elements_returned]
|
|
|
|
* or
|
|
|
|
* struct hv_24x7_result_element_v2[@num_elements_returned]
|
|
|
|
*
|
|
|
|
* depending on the interface_version field of the
|
|
|
|
* struct hv_24x7_data_result_buffer containing this result.
|
|
|
|
*/
|
|
|
|
char elements[];
|
2014-03-14 12:00:38 +07:00
|
|
|
} __packed;
|
|
|
|
|
|
|
|
struct hv_24x7_data_result_buffer {
|
|
|
|
/* See versioning for request buffer */
|
|
|
|
__u8 interface_version;
|
|
|
|
|
|
|
|
__u8 num_results;
|
|
|
|
__u8 reserved[0x1];
|
|
|
|
__u8 failing_request_ix;
|
|
|
|
__be32 detailed_rc;
|
|
|
|
__be64 cec_cfg_instance_id;
|
|
|
|
__be64 catalog_version_num;
|
|
|
|
__u8 reserved2[0x8];
|
|
|
|
/* WARNING: only valid for the first result due to variable sizes of
|
|
|
|
* results */
|
2017-06-30 04:55:37 +07:00
|
|
|
struct hv_24x7_result results[]; /* [@num_results] */
|
2014-03-14 12:00:38 +07:00
|
|
|
} __packed;
|
|
|
|
|
|
|
|
#endif
|