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 14:07:57 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2007-03-16 14:14:08 +00:00
|
|
|
config PPC_PSERIES
|
2009-03-10 17:53:27 +00:00
|
|
|
depends on PPC64 && PPC_BOOK3S
|
2007-03-16 14:14:08 +00:00
|
|
|
bool "IBM pSeries & new (POWER5-based) iSeries"
|
2011-06-01 18:05:09 +00:00
|
|
|
select HAVE_PCSPKR_PLATFORM
|
2007-03-16 14:14:08 +00:00
|
|
|
select MPIC
|
2012-02-16 03:38:40 +00:00
|
|
|
select OF_DYNAMIC
|
2018-11-15 19:05:32 +00:00
|
|
|
select FORCE_PCI
|
2009-11-27 06:33:58 +00:00
|
|
|
select PCI_MSI
|
2011-04-04 03:46:58 +00:00
|
|
|
select PPC_XICS
|
powerpc/xive: guest exploitation of the XIVE interrupt controller
This is the framework for using XIVE in a PowerVM guest. The support
is very similar to the native one in a much simpler form.
Each source is associated with an Event State Buffer (ESB). This is a
two bit state machine which is used to trigger events. The bits are
named "P" (pending) and "Q" (queued) and can be controlled by MMIO.
The Guest OS registers event (or notifications) queues on which the HW
will post event data for a target to notify.
Instead of OPAL calls, a set of Hypervisors call are used to configure
the interrupt sources and the event/notification queues of the guest:
- H_INT_GET_SOURCE_INFO
used to obtain the address of the MMIO page of the Event State
Buffer (PQ bits) entry associated with the source.
- H_INT_SET_SOURCE_CONFIG
assigns a source to a "target".
- H_INT_GET_SOURCE_CONFIG
determines to which "target" and "priority" is assigned to a source
- H_INT_GET_QUEUE_INFO
returns the address of the notification management page associated
with the specified "target" and "priority".
- H_INT_SET_QUEUE_CONFIG
sets or resets the event queue for a given "target" and "priority".
It is also used to set the notification config associated with the
queue, only unconditional notification for the moment. Reset is
performed with a queue size of 0 and queueing is disabled in that
case.
- H_INT_GET_QUEUE_CONFIG
returns the queue settings for a given "target" and "priority".
- H_INT_RESET
resets all of the partition's interrupt exploitation structures to
their initial state, losing all configuration set via the hcalls
H_INT_SET_SOURCE_CONFIG and H_INT_SET_QUEUE_CONFIG.
- H_INT_SYNC
issue a synchronisation on a source to make sure sure all
notifications have reached their queue.
As for XICS, the XIVE interface for the guest is described in the
device tree under the "interrupt-controller" node. A couple of new
properties are specific to XIVE :
- "reg"
contains the base address and size of the thread interrupt
managnement areas (TIMA), also called rings, for the User level and
for the Guest OS level. Only the Guest OS level is taken into
account today.
- "ibm,xive-eq-sizes"
the size of the event queues. One cell per size supported, contains
log2 of size, in ascending order.
- "ibm,xive-lisn-ranges"
the interrupt numbers ranges assigned to the guest. These are
allocated using a simple bitmap.
and also :
- "/ibm,plat-res-int-priorities"
contains a list of priorities that the hypervisor has reserved for
its own use.
Tested with a QEMU XIVE model for pseries and with the Power hypervisor.
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
2017-08-30 19:46:11 +00:00
|
|
|
select PPC_XIVE_SPAPR
|
2011-04-04 03:46:58 +00:00
|
|
|
select PPC_ICP_NATIVE
|
|
|
|
|
select PPC_ICP_HV
|
|
|
|
|
select PPC_ICS_RTAS
|
2007-03-16 14:14:08 +00:00
|
|
|
select PPC_I8259
|
|
|
|
|
select PPC_RTAS
|
2009-09-24 19:30:05 +00:00
|
|
|
select PPC_RTAS_DAEMON
|
2007-03-16 14:14:08 +00:00
|
|
|
select RTAS_ERROR_LOGGING
|
|
|
|
|
select PPC_UDBG_16550
|
2012-11-14 18:49:50 +00:00
|
|
|
select PPC_DOORBELL
|
2017-04-05 02:44:51 +00:00
|
|
|
select HOTPLUG_CPU
|
|
|
|
|
select FORCE_SMP
|
2019-05-07 06:25:59 +00:00
|
|
|
select SWIOTLB
|
2007-03-16 14:14:08 +00:00
|
|
|
default y
|
2005-09-26 06:04:21 +00:00
|
|
|
|
2022-09-02 08:53:14 +00:00
|
|
|
config PARAVIRT
|
|
|
|
|
bool
|
|
|
|
|
|
2020-07-24 13:14:21 +00:00
|
|
|
config PARAVIRT_SPINLOCKS
|
|
|
|
|
bool
|
|
|
|
|
|
2022-09-02 08:53:14 +00:00
|
|
|
config PARAVIRT_TIME_ACCOUNTING
|
|
|
|
|
select PARAVIRT
|
|
|
|
|
bool
|
|
|
|
|
|
2005-09-26 06:04:21 +00:00
|
|
|
config PPC_SPLPAR
|
|
|
|
|
bool "Support for shared-processor logical partitions"
|
2020-07-24 13:14:21 +00:00
|
|
|
depends on PPC_PSERIES
|
|
|
|
|
select PARAVIRT_SPINLOCKS if PPC_QUEUED_SPINLOCKS
|
2022-09-02 08:53:14 +00:00
|
|
|
select PARAVIRT_TIME_ACCOUNTING if VIRT_CPU_ACCOUNTING_GEN
|
2020-07-24 13:14:21 +00:00
|
|
|
default y
|
2005-09-26 06:04:21 +00:00
|
|
|
help
|
|
|
|
|
Enabling this option will make the kernel run more efficiently
|
|
|
|
|
on logically-partitioned pSeries systems which use shared
|
|
|
|
|
processors, that is, which share physical processors between
|
|
|
|
|
two or more partitions.
|
|
|
|
|
|
2020-07-24 13:14:21 +00:00
|
|
|
Say Y if you are unsure.
|
|
|
|
|
|
2014-05-13 03:09:55 +00:00
|
|
|
config DTL
|
|
|
|
|
bool "Dispatch Trace Log"
|
|
|
|
|
depends on PPC_SPLPAR && DEBUG_FS
|
|
|
|
|
help
|
|
|
|
|
SPLPAR machines can log hypervisor preempt & dispatch events to a
|
|
|
|
|
kernel buffer. Saying Y here will enable logging these events,
|
|
|
|
|
which are accessible through a debugfs file.
|
|
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
2010-10-06 08:37:09 +00:00
|
|
|
config PSERIES_ENERGY
|
|
|
|
|
tristate "pSeries energy management capabilities driver"
|
|
|
|
|
depends on PPC_PSERIES
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Provides interface to platform energy management capabilities
|
|
|
|
|
on supported PSERIES platforms.
|
|
|
|
|
Provides: /sys/devices/system/cpu/pseries_(de)activation_hint_list
|
|
|
|
|
and /sys/devices/system/cpu/cpuN/pseries_(de)activation_hint
|
|
|
|
|
|
2011-05-05 12:32:48 +00:00
|
|
|
config IO_EVENT_IRQ
|
|
|
|
|
bool "IO Event Interrupt support"
|
|
|
|
|
depends on PPC_PSERIES
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Select this option, if you want to enable support for IO Event
|
|
|
|
|
interrupts. IO event interrupt is a mechanism provided by RTAS
|
|
|
|
|
to return information about hardware error and non-error events
|
|
|
|
|
which may need OS attention. RTAS returns events for multiple
|
|
|
|
|
event types and scopes. Device drivers can register their handlers
|
|
|
|
|
to receive events.
|
|
|
|
|
|
|
|
|
|
This option will only enable the IO event platform code. You
|
|
|
|
|
will still need to enable or compile the actual drivers
|
2012-04-13 15:14:11 +00:00
|
|
|
that use this infrastructure to handle IO event interrupts.
|
2011-05-05 12:32:48 +00:00
|
|
|
|
|
|
|
|
Say Y if you are unsure.
|
|
|
|
|
|
2005-09-26 06:04:21 +00:00
|
|
|
config LPARCFG
|
2006-03-14 00:35:37 +00:00
|
|
|
bool "LPAR Configuration Data"
|
2012-02-22 14:10:12 +00:00
|
|
|
depends on PPC_PSERIES
|
2005-09-26 06:04:21 +00:00
|
|
|
help
|
2019-07-03 16:04:13 +00:00
|
|
|
Provide system capacity information via human readable
|
|
|
|
|
<key word>=<value> pairs through a /proc/ppc64/lparcfg interface.
|
2008-04-24 05:13:21 +00:00
|
|
|
|
|
|
|
|
config PPC_PSERIES_DEBUG
|
|
|
|
|
depends on PPC_PSERIES && PPC_EARLY_DEBUG
|
|
|
|
|
bool "Enable extra debug logging in platforms/pseries"
|
2019-07-03 16:04:13 +00:00
|
|
|
default y
|
|
|
|
|
help
|
2010-10-14 14:48:52 +00:00
|
|
|
Say Y here if you want the pseries core to produce a bunch of
|
|
|
|
|
debug messages to the system log. Select this if you are having a
|
|
|
|
|
problem with the pseries core and want to see more of what is
|
|
|
|
|
going on. This does not enable debugging in lpar.c, which must
|
|
|
|
|
be manually done due to its verbosity.
|
2008-07-23 18:30:29 +00:00
|
|
|
|
|
|
|
|
config PPC_SMLPAR
|
|
|
|
|
bool "Support for shared-memory logical partitions"
|
|
|
|
|
depends on PPC_PSERIES
|
|
|
|
|
select LPARCFG
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable shared memory partition support.
|
|
|
|
|
With this option a system running in an LPAR can be given more
|
|
|
|
|
memory than physically available and will allow firmware to
|
|
|
|
|
balance memory across many LPARs.
|
|
|
|
|
|
|
|
|
|
config CMM
|
|
|
|
|
tristate "Collaborative memory management"
|
2009-10-19 05:51:34 +00:00
|
|
|
depends on PPC_SMLPAR
|
2019-10-31 14:29:29 +00:00
|
|
|
select MEMORY_BALLOON
|
2008-07-23 18:30:29 +00:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Select this option, if you want to enable the kernel interface
|
|
|
|
|
to reduce the memory size of the system. This is accomplished
|
|
|
|
|
by allocating pages of memory and put them "on hold". This only
|
|
|
|
|
makes sense for a system running in an LPAR where the unused pages
|
|
|
|
|
will be reused for other LPARs. The interface allows firmware to
|
|
|
|
|
balance memory across many LPARs.
|
2009-03-11 17:55:52 +00:00
|
|
|
|
2014-03-14 05:00:43 +00:00
|
|
|
config HV_PERF_CTRS
|
2019-07-03 16:04:13 +00:00
|
|
|
bool "Hypervisor supplied PMU events (24x7 & GPCI)"
|
|
|
|
|
default y
|
|
|
|
|
depends on PERF_EVENTS && PPC_PSERIES
|
|
|
|
|
help
|
2014-03-14 05:00:43 +00:00
|
|
|
Enable access to hypervisor supplied counters in perf. Currently,
|
|
|
|
|
this enables code that uses the hcall GetPerfCounterInfo and 24x7
|
|
|
|
|
interfaces to retrieve counters. GPCI exists on Power 6 and later
|
2017-06-29 21:55:37 +00:00
|
|
|
systems. 24x7 is available on Power 8 and later systems.
|
2014-03-14 05:00:43 +00:00
|
|
|
|
2019-07-03 16:04:13 +00:00
|
|
|
If unsure, select Y.
|
2016-11-15 03:47:42 +00:00
|
|
|
|
|
|
|
|
config IBMVIO
|
|
|
|
|
depends on PPC_PSERIES
|
|
|
|
|
bool
|
|
|
|
|
default y
|
2016-11-15 03:47:43 +00:00
|
|
|
|
|
|
|
|
config IBMEBUS
|
2016-11-15 03:47:44 +00:00
|
|
|
depends on PPC_PSERIES && !CPU_LITTLE_ENDIAN
|
2016-11-15 03:47:43 +00:00
|
|
|
bool "Support for GX bus based adapters"
|
|
|
|
|
help
|
|
|
|
|
Bus device driver for GX bus based adapters.
|
2018-10-14 23:18:28 +00:00
|
|
|
|
2022-07-23 11:30:46 +00:00
|
|
|
config PSERIES_PLPKS
|
|
|
|
|
depends on PPC_PSERIES
|
|
|
|
|
bool "Support for the Platform Key Storage"
|
|
|
|
|
help
|
|
|
|
|
PowerVM provides an isolated Platform Keystore(PKS) storage
|
|
|
|
|
allocation for each LPAR with individually managed access
|
|
|
|
|
controls to store sensitive information securely. It can be
|
|
|
|
|
used to store asymmetric public keys or secrets as required
|
|
|
|
|
by different usecases. Select this config to enable
|
|
|
|
|
operating system interface to hypervisor to access this space.
|
|
|
|
|
|
|
|
|
|
If unsure, select N.
|
|
|
|
|
|
2018-10-14 23:18:28 +00:00
|
|
|
config PAPR_SCM
|
2018-12-06 15:17:08 +00:00
|
|
|
depends on PPC_PSERIES && MEMORY_HOTPLUG && LIBNVDIMM
|
2018-10-14 23:18:28 +00:00
|
|
|
tristate "Support for the PAPR Storage Class Memory interface"
|
|
|
|
|
help
|
|
|
|
|
Enable access to hypervisor provided storage class memory.
|
2019-08-20 02:13:12 +00:00
|
|
|
|
|
|
|
|
config PPC_SVM
|
|
|
|
|
bool "Secure virtual machine (SVM) support for POWER"
|
|
|
|
|
depends on PPC_PSERIES
|
2019-08-20 02:13:24 +00:00
|
|
|
select SWIOTLB
|
|
|
|
|
select ARCH_HAS_MEM_ENCRYPT
|
|
|
|
|
select ARCH_HAS_FORCE_DMA_UNENCRYPTED
|
2021-09-08 22:58:35 +00:00
|
|
|
select ARCH_HAS_CC_PLATFORM
|
2019-08-20 02:13:12 +00:00
|
|
|
help
|
|
|
|
|
There are certain POWER platforms which support secure guests using
|
|
|
|
|
the Protected Execution Facility, with the help of an Ultravisor
|
|
|
|
|
executing below the hypervisor layer. This enables support for
|
|
|
|
|
those guests.
|
|
|
|
|
|
|
|
|
|
If unsure, say "N".
|