mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-21 18:38:46 +07:00
b24413180f
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>
209 lines
5.9 KiB
Plaintext
209 lines
5.9 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
#
|
|
# KVM configuration
|
|
#
|
|
|
|
source "virt/kvm/Kconfig"
|
|
|
|
menuconfig VIRTUALIZATION
|
|
bool "Virtualization"
|
|
---help---
|
|
Say Y here to get to see options for using your Linux host to run
|
|
other operating systems inside virtual machines (guests).
|
|
This option alone does not add any kernel code.
|
|
|
|
If you say N, all options in this submenu will be skipped and
|
|
disabled.
|
|
|
|
if VIRTUALIZATION
|
|
|
|
config KVM
|
|
bool
|
|
select PREEMPT_NOTIFIERS
|
|
select ANON_INODES
|
|
select HAVE_KVM_EVENTFD
|
|
select SRCU
|
|
select KVM_VFIO
|
|
select IRQ_BYPASS_MANAGER
|
|
select HAVE_KVM_IRQ_BYPASS
|
|
|
|
config KVM_BOOK3S_HANDLER
|
|
bool
|
|
|
|
config KVM_BOOK3S_32_HANDLER
|
|
bool
|
|
select KVM_BOOK3S_HANDLER
|
|
select KVM_MMIO
|
|
|
|
config KVM_BOOK3S_64_HANDLER
|
|
bool
|
|
select KVM_BOOK3S_HANDLER
|
|
|
|
config KVM_BOOK3S_PR_POSSIBLE
|
|
bool
|
|
select KVM_MMIO
|
|
select MMU_NOTIFIER
|
|
|
|
config KVM_BOOK3S_HV_POSSIBLE
|
|
bool
|
|
|
|
config KVM_BOOK3S_32
|
|
tristate "KVM support for PowerPC book3s_32 processors"
|
|
depends on PPC_BOOK3S_32 && !SMP && !PTE_64BIT
|
|
select KVM
|
|
select KVM_BOOK3S_32_HANDLER
|
|
select KVM_BOOK3S_PR_POSSIBLE
|
|
---help---
|
|
Support running unmodified book3s_32 guest kernels
|
|
in virtual machines on book3s_32 host processors.
|
|
|
|
This module provides access to the hardware capabilities through
|
|
a character device node named /dev/kvm.
|
|
|
|
If unsure, say N.
|
|
|
|
config KVM_BOOK3S_64
|
|
tristate "KVM support for PowerPC book3s_64 processors"
|
|
depends on PPC_BOOK3S_64
|
|
select KVM_BOOK3S_64_HANDLER
|
|
select KVM
|
|
select KVM_BOOK3S_PR_POSSIBLE if !KVM_BOOK3S_HV_POSSIBLE
|
|
select SPAPR_TCE_IOMMU if IOMMU_SUPPORT && (PPC_SERIES || PPC_POWERNV)
|
|
---help---
|
|
Support running unmodified book3s_64 and book3s_32 guest kernels
|
|
in virtual machines on book3s_64 host processors.
|
|
|
|
This module provides access to the hardware capabilities through
|
|
a character device node named /dev/kvm.
|
|
|
|
If unsure, say N.
|
|
|
|
config KVM_BOOK3S_64_HV
|
|
tristate "KVM for POWER7 and later using hypervisor mode in host"
|
|
depends on KVM_BOOK3S_64 && PPC_POWERNV
|
|
select KVM_BOOK3S_HV_POSSIBLE
|
|
select MMU_NOTIFIER
|
|
select CMA
|
|
---help---
|
|
Support running unmodified book3s_64 guest kernels in
|
|
virtual machines on POWER7 and newer processors that have
|
|
hypervisor mode available to the host.
|
|
|
|
If you say Y here, KVM will use the hardware virtualization
|
|
facilities of POWER7 (and later) processors, meaning that
|
|
guest operating systems will run at full hardware speed
|
|
using supervisor and user modes. However, this also means
|
|
that KVM is not usable under PowerVM (pHyp), is only usable
|
|
on POWER7 or later processors, and cannot emulate a
|
|
different processor from the host processor.
|
|
|
|
If unsure, say N.
|
|
|
|
config KVM_BOOK3S_64_PR
|
|
tristate "KVM support without using hypervisor mode in host"
|
|
depends on KVM_BOOK3S_64
|
|
select KVM_BOOK3S_PR_POSSIBLE
|
|
---help---
|
|
Support running guest kernels in virtual machines on processors
|
|
without using hypervisor mode in the host, by running the
|
|
guest in user mode (problem state) and emulating all
|
|
privileged instructions and registers.
|
|
|
|
This is not as fast as using hypervisor mode, but works on
|
|
machines where hypervisor mode is not available or not usable,
|
|
and can emulate processors that are different from the host
|
|
processor, including emulating 32-bit processors on a 64-bit
|
|
host.
|
|
|
|
config KVM_BOOK3S_HV_EXIT_TIMING
|
|
bool "Detailed timing for hypervisor real-mode code"
|
|
depends on KVM_BOOK3S_HV_POSSIBLE && DEBUG_FS
|
|
---help---
|
|
Calculate time taken for each vcpu in the real-mode guest entry,
|
|
exit, and interrupt handling code, plus time spent in the guest
|
|
and in nap mode due to idle (cede) while other threads are still
|
|
in the guest. The total, minimum and maximum times in nanoseconds
|
|
together with the number of executions are reported in debugfs in
|
|
kvm/vm#/vcpu#/timings. The overhead is of the order of 30 - 40
|
|
ns per exit on POWER8.
|
|
|
|
If unsure, say N.
|
|
|
|
config KVM_BOOKE_HV
|
|
bool
|
|
|
|
config KVM_EXIT_TIMING
|
|
bool "Detailed exit timing"
|
|
depends on KVM_E500V2 || KVM_E500MC
|
|
---help---
|
|
Calculate elapsed time for every exit/enter cycle. A per-vcpu
|
|
report is available in debugfs kvm/vm#_vcpu#_timing.
|
|
The overhead is relatively small, however it is not recommended for
|
|
production environments.
|
|
|
|
If unsure, say N.
|
|
|
|
config KVM_E500V2
|
|
bool "KVM support for PowerPC E500v2 processors"
|
|
depends on E500 && !PPC_E500MC
|
|
select KVM
|
|
select KVM_MMIO
|
|
select MMU_NOTIFIER
|
|
---help---
|
|
Support running unmodified E500 guest kernels in virtual machines on
|
|
E500v2 host processors.
|
|
|
|
This module provides access to the hardware capabilities through
|
|
a character device node named /dev/kvm.
|
|
|
|
If unsure, say N.
|
|
|
|
config KVM_E500MC
|
|
bool "KVM support for PowerPC E500MC/E5500/E6500 processors"
|
|
depends on PPC_E500MC
|
|
select KVM
|
|
select KVM_MMIO
|
|
select KVM_BOOKE_HV
|
|
select MMU_NOTIFIER
|
|
---help---
|
|
Support running unmodified E500MC/E5500/E6500 guest kernels in
|
|
virtual machines on E500MC/E5500/E6500 host processors.
|
|
|
|
This module provides access to the hardware capabilities through
|
|
a character device node named /dev/kvm.
|
|
|
|
If unsure, say N.
|
|
|
|
config KVM_MPIC
|
|
bool "KVM in-kernel MPIC emulation"
|
|
depends on KVM && E500
|
|
select HAVE_KVM_IRQCHIP
|
|
select HAVE_KVM_IRQFD
|
|
select HAVE_KVM_IRQ_ROUTING
|
|
select HAVE_KVM_MSI
|
|
help
|
|
Enable support for emulating MPIC devices inside the
|
|
host kernel, rather than relying on userspace to emulate.
|
|
Currently, support is limited to certain versions of
|
|
Freescale's MPIC implementation.
|
|
|
|
config KVM_XICS
|
|
bool "KVM in-kernel XICS emulation"
|
|
depends on KVM_BOOK3S_64 && !KVM_MPIC
|
|
select HAVE_KVM_IRQCHIP
|
|
select HAVE_KVM_IRQFD
|
|
default y
|
|
---help---
|
|
Include support for the XICS (eXternal Interrupt Controller
|
|
Specification) interrupt controller architecture used on
|
|
IBM POWER (pSeries) servers.
|
|
|
|
config KVM_XIVE
|
|
bool
|
|
default y
|
|
depends on KVM_XICS && PPC_XIVE_NATIVE && KVM_BOOK3S_HV_POSSIBLE
|
|
|
|
source drivers/vhost/Kconfig
|
|
|
|
endif # VIRTUALIZATION
|