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 */
|
2008-10-23 13:26:29 +08:00
|
|
|
#ifndef _ASM_X86_IRQ_VECTORS_H
|
|
|
|
|
#define _ASM_X86_IRQ_VECTORS_H
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2011-01-17 10:52:02 +08:00
|
|
|
#include <linux/threads.h>
|
2009-01-31 09:48:17 +08:00
|
|
|
/*
|
|
|
|
|
* Linux IRQ vector layout.
|
|
|
|
|
*
|
|
|
|
|
* There are 256 IDT entries (per CPU - each entry is 8 bytes) which can
|
|
|
|
|
* be defined by Linux. They are used as a jump table by the CPU when a
|
|
|
|
|
* given vector is triggered - by a CPU-external, CPU-internal or
|
|
|
|
|
* software-triggered event.
|
|
|
|
|
*
|
|
|
|
|
* Linux sets the kernel code address each entry jumps to early during
|
|
|
|
|
* bootup, and never changes them. This is the general layout of the
|
|
|
|
|
* IDT entries:
|
|
|
|
|
*
|
|
|
|
|
* Vectors 0 ... 31 : system traps and exceptions - hardcoded events
|
|
|
|
|
* Vectors 32 ... 127 : device interrupts
|
|
|
|
|
* Vector 128 : legacy int80 syscall interface
|
2019-04-22 10:49:43 +08:00
|
|
|
* Vectors 129 ... LOCAL_TIMER_VECTOR-1
|
|
|
|
|
* Vectors LOCAL_TIMER_VECTOR ... 255 : special interrupts
|
2009-01-31 09:48:17 +08:00
|
|
|
*
|
|
|
|
|
* 64-bit x86 has per CPU IDT tables, 32-bit has one shared IDT table.
|
|
|
|
|
*
|
|
|
|
|
* This file enumerates the exact layout of them:
|
|
|
|
|
*/
|
|
|
|
|
|
2021-05-20 05:21:49 +08:00
|
|
|
/* This is used as an interrupt vector when programming the APIC. */
|
2009-01-31 09:48:17 +08:00
|
|
|
#define NMI_VECTOR 0x02
|
2008-05-03 02:10:09 +08:00
|
|
|
|
|
|
|
|
/*
|
2010-01-14 08:19:11 +08:00
|
|
|
* IDT vectors usable for external interrupt sources start at 0x20.
|
|
|
|
|
* (0x80 is the syscall vector, 0x30-0x3f are for ISA)
|
2008-05-03 02:10:09 +08:00
|
|
|
*/
|
2010-01-14 08:19:11 +08:00
|
|
|
#define FIRST_EXTERNAL_VECTOR 0x20
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Reserve the lowest usable vector (and hence lowest priority) 0x20 for
|
|
|
|
|
* triggering cleanup after irq migration. 0x21-0x2f will still be used
|
|
|
|
|
* for device interrupts.
|
|
|
|
|
*/
|
|
|
|
|
#define IRQ_MOVE_CLEANUP_VECTOR FIRST_EXTERNAL_VECTOR
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2010-01-05 08:16:06 +08:00
|
|
|
#define IA32_SYSCALL_VECTOR 0x80
|
2008-05-03 02:10:09 +08:00
|
|
|
|
|
|
|
|
/*
|
2010-01-14 08:19:11 +08:00
|
|
|
* Vectors 0x30-0x3f are used for ISA interrupts.
|
2010-01-05 08:16:06 +08:00
|
|
|
* round up to the next 16-vector boundary
|
2008-05-03 02:10:09 +08:00
|
|
|
*/
|
2015-05-09 23:36:53 +08:00
|
|
|
#define ISA_IRQ_VECTOR(irq) (((FIRST_EXTERNAL_VECTOR + 16) & ~15) + irq)
|
2008-05-03 02:10:09 +08:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Special IRQ vectors used by the SMP architecture, 0xf0-0xff
|
|
|
|
|
*
|
|
|
|
|
* some of the following vectors are 'rare', they are merged
|
|
|
|
|
* into a single vector (CALL_FUNCTION_VECTOR) to save vector space.
|
|
|
|
|
* TLB, reschedule and local APIC vectors are performance-critical.
|
|
|
|
|
*/
|
2009-01-21 16:26:06 +08:00
|
|
|
|
2009-01-31 09:10:03 +08:00
|
|
|
#define SPURIOUS_APIC_VECTOR 0xff
|
2009-01-31 09:06:50 +08:00
|
|
|
/*
|
|
|
|
|
* Sanity check
|
|
|
|
|
*/
|
|
|
|
|
#if ((SPURIOUS_APIC_VECTOR & 0x0F) != 0x0F)
|
|
|
|
|
# error SPURIOUS_APIC_VECTOR definition error
|
|
|
|
|
#endif
|
|
|
|
|
|
2009-01-31 09:10:03 +08:00
|
|
|
#define ERROR_APIC_VECTOR 0xfe
|
|
|
|
|
#define RESCHEDULE_VECTOR 0xfd
|
|
|
|
|
#define CALL_FUNCTION_VECTOR 0xfc
|
|
|
|
|
#define CALL_FUNCTION_SINGLE_VECTOR 0xfb
|
|
|
|
|
#define THERMAL_APIC_VECTOR 0xfa
|
2009-04-29 05:32:56 +08:00
|
|
|
#define THRESHOLD_APIC_VECTOR 0xf9
|
x86: fix panic with interrupts off (needed for MCE)
For some time each panic() called with interrupts disabled
triggered the !irqs_disabled() WARN_ON in smp_call_function(),
producing ugly backtraces and confusing users.
This is a common situation with machine checks for example which
tend to call panic with interrupts disabled, but will also hit
in other situations e.g. panic during early boot. In fact it
means that panic cannot be called in many circumstances, which
would be bad.
This all started with the new fancy queued smp_call_function,
which is then used by the shutdown path to shut down the other
CPUs.
On closer examination it turned out that the fancy RCU
smp_call_function() does lots of things not suitable in a panic
situation anyways, like allocating memory and relying on complex
system state.
I originally tried to patch this over by checking for panic
there, but it was quite complicated and the original patch
was also not very popular. This also didn't fix some of the
underlying complexity problems.
The new code in post 2.6.29 tries to patch around this by
checking for oops_in_progress, but that is not enough to make
this fully safe and I don't think that's a real solution
because panic has to be reliable.
So instead use an own vector to reboot. This makes the reboot
code extremly straight forward, which is definitely a big plus
in a panic situation where it is important to avoid relying on
too much kernel state. The new simple code is also safe to be
called from interupts off region because it is very very simple.
There can be situations where it is important that panic
is reliable. For example on a fatal machine check the panic
is needed to get the system up again and running as quickly
as possible. So it's important that panic is reliable and
all function it calls simple.
This is why I came up with this simple vector scheme.
It's very hard to beat in simplicity. Vectors are not
particularly precious anymore since all big systems are
using per CPU vectors.
Another possibility would have been to use an NMI similar
to kdump, but there is still the problem that NMIs don't
work reliably on some systems due to BIOS issues. NMIs
would have been able to stop CPUs running with interrupts
off too. In the sake of universal reliability I opted for
using a non NMI vector for now.
I put the reboot vector into the highest priority bucket of
the APIC vectors and moved the 64bit UV_BAU message down
instead into the next lower priority.
[ Impact: bug fix, fixes an old regression ]
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2009-05-28 03:56:52 +08:00
|
|
|
#define REBOOT_VECTOR 0xf8
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2009-01-31 09:23:27 +08:00
|
|
|
/*
|
2009-03-05 02:56:05 +08:00
|
|
|
* Generic system vector for platform specific use
|
2009-01-31 09:23:27 +08:00
|
|
|
*/
|
2011-01-17 10:52:02 +08:00
|
|
|
#define X86_PLATFORM_IPI_VECTOR 0xf7
|
2009-01-31 09:23:27 +08:00
|
|
|
|
2009-03-05 02:56:05 +08:00
|
|
|
/*
|
2010-10-14 14:01:34 +08:00
|
|
|
* IRQ work vector:
|
2009-03-05 02:56:05 +08:00
|
|
|
*/
|
2011-01-17 10:52:02 +08:00
|
|
|
#define IRQ_WORK_VECTOR 0xf6
|
2009-03-05 02:56:05 +08:00
|
|
|
|
2021-05-20 05:21:49 +08:00
|
|
|
/* 0xf5 - unused, was UV_BAU_MESSAGE */
|
2015-05-06 19:58:56 +08:00
|
|
|
#define DEFERRED_ERROR_VECTOR 0xf4
|
x86: fix panic with interrupts off (needed for MCE)
For some time each panic() called with interrupts disabled
triggered the !irqs_disabled() WARN_ON in smp_call_function(),
producing ugly backtraces and confusing users.
This is a common situation with machine checks for example which
tend to call panic with interrupts disabled, but will also hit
in other situations e.g. panic during early boot. In fact it
means that panic cannot be called in many circumstances, which
would be bad.
This all started with the new fancy queued smp_call_function,
which is then used by the shutdown path to shut down the other
CPUs.
On closer examination it turned out that the fancy RCU
smp_call_function() does lots of things not suitable in a panic
situation anyways, like allocating memory and relying on complex
system state.
I originally tried to patch this over by checking for panic
there, but it was quite complicated and the original patch
was also not very popular. This also didn't fix some of the
underlying complexity problems.
The new code in post 2.6.29 tries to patch around this by
checking for oops_in_progress, but that is not enough to make
this fully safe and I don't think that's a real solution
because panic has to be reliable.
So instead use an own vector to reboot. This makes the reboot
code extremly straight forward, which is definitely a big plus
in a panic situation where it is important to avoid relying on
too much kernel state. The new simple code is also safe to be
called from interupts off region because it is very very simple.
There can be situations where it is important that panic
is reliable. For example on a fatal machine check the panic
is needed to get the system up again and running as quickly
as possible. So it's important that panic is reliable and
all function it calls simple.
This is why I came up with this simple vector scheme.
It's very hard to beat in simplicity. Vectors are not
particularly precious anymore since all big systems are
using per CPU vectors.
Another possibility would have been to use an NMI similar
to kdump, but there is still the problem that NMIs don't
work reliably on some systems due to BIOS issues. NMIs
would have been able to stop CPUs running with interrupts
off too. In the sake of universal reliability I opted for
using a non NMI vector for now.
I put the reboot vector into the highest priority bucket of
the APIC vectors and moved the 64bit UV_BAU message down
instead into the next lower priority.
[ Impact: bug fix, fixes an old regression ]
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2009-05-28 03:56:52 +08:00
|
|
|
|
2013-02-04 09:22:39 +08:00
|
|
|
/* Vector on which hypervisor callbacks will be delivered */
|
|
|
|
|
#define HYPERVISOR_CALLBACK_VECTOR 0xf3
|
2011-01-17 10:52:02 +08:00
|
|
|
|
2015-05-06 19:58:57 +08:00
|
|
|
/* Vector for KVM to deliver posted interrupt IPI */
|
|
|
|
|
#ifdef CONFIG_HAVE_KVM
|
|
|
|
|
#define POSTED_INTR_VECTOR 0xf2
|
2017-04-28 13:13:58 +08:00
|
|
|
#define POSTED_INTR_WAKEUP_VECTOR 0xf1
|
|
|
|
|
#define POSTED_INTR_NESTED_VECTOR 0xf0
|
2015-05-06 19:58:57 +08:00
|
|
|
#endif
|
|
|
|
|
|
2017-09-14 05:29:50 +08:00
|
|
|
#define MANAGED_IRQ_SHUTDOWN_VECTOR 0xef
|
2018-01-24 21:23:33 +08:00
|
|
|
|
|
|
|
|
#if IS_ENABLED(CONFIG_HYPERV)
|
|
|
|
|
#define HYPERV_REENLIGHTENMENT_VECTOR 0xee
|
2018-03-05 13:17:18 +08:00
|
|
|
#define HYPERV_STIMER0_VECTOR 0xed
|
2018-01-24 21:23:33 +08:00
|
|
|
#endif
|
|
|
|
|
|
2018-03-05 13:17:18 +08:00
|
|
|
#define LOCAL_TIMER_VECTOR 0xec
|
2011-01-17 10:52:02 +08:00
|
|
|
|
2009-01-31 09:48:17 +08:00
|
|
|
#define NR_VECTORS 256
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2014-11-03 16:39:43 +08:00
|
|
|
#ifdef CONFIG_X86_LOCAL_APIC
|
|
|
|
|
#define FIRST_SYSTEM_VECTOR LOCAL_TIMER_VECTOR
|
|
|
|
|
#else
|
|
|
|
|
#define FIRST_SYSTEM_VECTOR NR_VECTORS
|
|
|
|
|
#endif
|
|
|
|
|
|
2021-05-20 05:21:48 +08:00
|
|
|
#define NR_EXTERNAL_VECTORS (FIRST_SYSTEM_VECTOR - FIRST_EXTERNAL_VECTOR)
|
|
|
|
|
#define NR_SYSTEM_VECTORS (NR_VECTORS - FIRST_SYSTEM_VECTOR)
|
|
|
|
|
|
2009-01-31 09:56:44 +08:00
|
|
|
/*
|
|
|
|
|
* Size the maximum number of interrupts.
|
|
|
|
|
*
|
|
|
|
|
* If the irq_desc[] array has a sparse layout, we can size things
|
|
|
|
|
* generously - it scales up linearly with the maximum number of CPUs,
|
|
|
|
|
* and the maximum number of IO-APICs, whichever is higher.
|
|
|
|
|
*
|
|
|
|
|
* In other cases we size more conservatively, to not create too large
|
|
|
|
|
* static arrays.
|
|
|
|
|
*/
|
|
|
|
|
|
2015-04-14 10:30:04 +08:00
|
|
|
#define NR_IRQS_LEGACY 16
|
2008-12-06 10:58:32 +08:00
|
|
|
|
2015-04-14 10:30:04 +08:00
|
|
|
#define CPU_VECTOR_LIMIT (64 * NR_CPUS)
|
|
|
|
|
#define IO_APIC_VECTOR_LIMIT (32 * MAX_IO_APICS)
|
2009-01-31 09:56:44 +08:00
|
|
|
|
2015-04-14 10:30:04 +08:00
|
|
|
#if defined(CONFIG_X86_IO_APIC) && defined(CONFIG_PCI_MSI)
|
|
|
|
|
#define NR_IRQS \
|
2009-01-31 09:56:44 +08:00
|
|
|
(CPU_VECTOR_LIMIT > IO_APIC_VECTOR_LIMIT ? \
|
|
|
|
|
(NR_VECTORS + CPU_VECTOR_LIMIT) : \
|
|
|
|
|
(NR_VECTORS + IO_APIC_VECTOR_LIMIT))
|
2015-04-14 10:30:04 +08:00
|
|
|
#elif defined(CONFIG_X86_IO_APIC)
|
|
|
|
|
#define NR_IRQS (NR_VECTORS + IO_APIC_VECTOR_LIMIT)
|
|
|
|
|
#elif defined(CONFIG_PCI_MSI)
|
|
|
|
|
#define NR_IRQS (NR_VECTORS + CPU_VECTOR_LIMIT)
|
|
|
|
|
#else
|
|
|
|
|
#define NR_IRQS NR_IRQS_LEGACY
|
2008-11-05 06:10:13 +08:00
|
|
|
#endif
|
2008-05-03 02:10:09 +08:00
|
|
|
|
2008-10-23 13:26:29 +08:00
|
|
|
#endif /* _ASM_X86_IRQ_VECTORS_H */
|