kernel February 2021

kernel@lists.fedoraproject.org

24 participants
153 discussions

[OS-BUILD PATCHv3 0/2] [redhat] New configs in drivers/perf
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: CKI Gitlab on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/797 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARM_DMC620_PMU: Support for PMU events monitoring on the ARM DMC-620 memory controller. Symbol: ARM_DMC620_PMU [=n] Type : tristate Defined at drivers/perf/Kconfig:133 Prompt: Enable PMU support for the ARM DMC-620 memory controller Depends on: PERF_EVENTS [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n]) Location: -> Device Drivers -> Performance monitor support --- Cc: Mark Salter <msalter(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Cc: Jeremy Linton <jlinton(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>

1 2

[OS-BUILD PATCHv2] [redhat] New configs in arch/arm64
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in arch/arm64 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARCH_N5X: This enables support for Intel's eASIC N5X SoCFPGA Family. Symbol: ARCH_N5X [=n] Type : bool Defined at arch/arm64/Kconfig.platforms:16 Prompt: Intel's eASIC N5X SoCFPGA Family Location: -> Platform selection --- Cc: Mark Salter <msalter(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Cc: Jeremy Linton <jlinton(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/arm/aarch64/CONFIG_ARCH_N5X b/redhat/configs/common/generic/arm/aarch64/CONFIG_ARCH_N5X --- /dev/null +++ b/redhat/configs/common/generic/arm/aarch64/CONFIG_ARCH_N5X @@ -0,0 +1 @@ +# CONFIG_ARCH_N5X is not set diff a/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X b/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X --- a/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X +++ /dev/null @@ -1,14 +0,0 @@ -# CONFIG_ARCH_N5X: -# -# This enables support for Intel's eASIC N5X SoCFPGA Family. -# -# Symbol: ARCH_N5X [=n] -# Type : bool -# Defined at arch/arm64/Kconfig.platforms:16 -# Prompt: Intel's eASIC N5X SoCFPGA Family -# Location: -# -> Platform selection -# -# -# -# CONFIG_ARCH_N5X is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/899

2 1

[OS-BUILD PATCHv2] [redhat] New configs in drivers/powercap
by CKI Gitlab (via Email Bridge) 23 Feb '21

23 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/powercap Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DTPM: This enables support for the power capping for the dynamic thermal power management userspace engine. Symbol: DTPM [=n] Type : bool Defined at drivers/powercap/Kconfig:47 Prompt: Power capping for Dynamic Thermal Power Management Depends on: POWERCAP [=y] Location: -> Device Drivers -> Generic powercap sysfs driver (POWERCAP [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_DTPM b/redhat/configs/common/generic/CONFIG_DTPM --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DTPM @@ -0,0 +1 @@ +# CONFIG_DTPM is not set diff a/redhat/configs/pending-common/generic/CONFIG_DTPM b/redhat/configs/pending-common/generic/CONFIG_DTPM --- a/redhat/configs/pending-common/generic/CONFIG_DTPM +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_DTPM: -# -# This enables support for the power capping for the dynamic -# thermal power management userspace engine. -# -# Symbol: DTPM [=n] -# Type : bool -# Defined at drivers/powercap/Kconfig:47 -# Prompt: Power capping for Dynamic Thermal Power Management -# Depends on: POWERCAP [=y] -# Location: -# -> Device Drivers -# -> Generic powercap sysfs driver (POWERCAP [=y]) -# -# -# -# CONFIG_DTPM is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/910

1 0

[OS-BUILD PATCHv2 0/2] [redhat] New configs in drivers/perf
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

3 4

[OS-BUILD PATCH] [redhat] New configs in arch/arm64
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in arch/arm64 Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_ARCH_N5X: This enables support for Intel's eASIC N5X SoCFPGA Family. Symbol: ARCH_N5X [=n] Type : bool Defined at arch/arm64/Kconfig.platforms:16 Prompt: Intel's eASIC N5X SoCFPGA Family Location: -> Platform selection --- Cc: Mark Salter <msalter(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Cc: Jeremy Linton <jlinton(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_ARCH_N5X b/redhat/configs/common/generic/CONFIG_ARCH_N5X --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_ARCH_N5X @@ -0,0 +1 @@ +# CONFIG_ARCH_N5X is not set diff a/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X b/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X --- a/redhat/configs/pending-common/generic/CONFIG_ARCH_N5X +++ /dev/null @@ -1,14 +0,0 @@ -# CONFIG_ARCH_N5X: -# -# This enables support for Intel's eASIC N5X SoCFPGA Family. -# -# Symbol: ARCH_N5X [=n] -# Type : bool -# Defined at arch/arm64/Kconfig.platforms:16 -# Prompt: Intel's eASIC N5X SoCFPGA Family -# Location: -# -> Platform selection -# -# -# -# CONFIG_ARCH_N5X is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/899

2 1

[OS-BUILD PATCH] [redhat] New configs in net/netfilter
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in net/netfilter Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_IP_VS_TWOS: The weighted random twos choice least-connection scheduling algorithm picks two random real servers and directs network connections to the server with the least active connections normalized by the server weight. If you want to compile it in kernel, say Y. To compile it as a module, choose M here. If unsure, say N. Symbol: IP_VS_TWOS [=n] Type : tristate Defined at net/netfilter/ipvs/Kconfig:274 Prompt: weighted random twos choice least-connection scheduling Depends on: NET [=y] && NETFILTER [=y] && IP_VS [=m] Location: -> Networking support (NET [=y]) -> Networking options -> Network packet filtering framework (Netfilter) (NETFILTER [=y]) -> IP virtual server support (IP_VS [=m]) --- Cc: Florian Westphal <fwestpha(a)redhat.com> Cc: Jiri Benc <jbenc(a)redhat.com> Cc: Marcelo Leitner <mleitner(a)redhat.com> Cc: Antoine Tenart <atenart(a)redhat.com> Cc: Balazs Nemeth <bnemeth(a)redhat.com> Cc: Davide Caratti <dcaratti(a)redhat.com> Cc: Eric Garver <egarver(a)redhat.com> Cc: Flavio Leitner <fbl(a)redhat.com> Cc: Guillaume Nault <gnault(a)redhat.com> Cc: Hangbin Liu <haliu(a)redhat.com> Cc: Ivan Vecera <ivecera(a)redhat.com> Cc: Jarod Wilson <jarod(a)redhat.com> Cc: Lorenzo Bianconi <lorenzo.bianconi(a)redhat.com> Cc: Paolo Abeni <pabeni(a)redhat.com> Cc: Phil Sutter <psutter(a)redhat.com> Cc: Sabrina Dubroca <sdubroca(a)redhat.com> Cc: Stefano Brivio <sbrivio(a)redhat.com> Cc: Xin Long <lxin(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_IP_VS_TWOS b/redhat/configs/common/generic/CONFIG_IP_VS_TWOS --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_IP_VS_TWOS @@ -0,0 +1 @@ +# CONFIG_IP_VS_TWOS is not set diff a/redhat/configs/pending-common/generic/CONFIG_IP_VS_TWOS b/redhat/configs/pending-common/generic/CONFIG_IP_VS_TWOS --- a/redhat/configs/pending-common/generic/CONFIG_IP_VS_TWOS +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_IP_VS_TWOS: -# -# The weighted random twos choice least-connection scheduling -# algorithm picks two random real servers and directs network -# connections to the server with the least active connections -# normalized by the server weight. -# -# If you want to compile it in kernel, say Y. To compile it as a -# module, choose M here. If unsure, say N. -# -# Symbol: IP_VS_TWOS [=n] -# Type : tristate -# Defined at net/netfilter/ipvs/Kconfig:274 -# Prompt: weighted random twos choice least-connection scheduling -# Depends on: NET [=y] && NETFILTER [=y] && IP_VS [=m] -# Location: -# -> Networking support (NET [=y]) -# -> Networking options -# -> Network packet filtering framework (Netfilter) (NETFILTER [=y]) -# -> IP virtual server support (IP_VS [=m]) -# -# -# -# CONFIG_IP_VS_TWOS is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/913

2 1

[OS-BUILD PATCH] [redhat] New configs in drivers/net/wireless
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/net/wireless Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_MT7921E: This adds support for MT7921E 802.11ax 2x2:2SS wireless devices. To compile this driver as a module, choose M here. Symbol: MT7921E [=n] Type : tristate Defined at drivers/net/wireless/mediatek/mt76/mt7921/Kconfig:2 Prompt: MediaTek MT7921E (PCIe) support Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && PCI [=y] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> Wireless LAN (WLAN [=y]) -> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y]) Selects: MT76_CONNAC_LIB [=n] && WANT_DEV_COREDUMP [=y] --- Cc: Jarod Wilson <jarod(a)redhat.com> Cc: John Linville <linville(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_MT7921E b/redhat/configs/common/generic/CONFIG_MT7921E --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_MT7921E @@ -0,0 +1 @@ +# CONFIG_MT7921E is not set diff a/redhat/configs/pending-common/generic/CONFIG_MT7921E b/redhat/configs/pending-common/generic/CONFIG_MT7921E --- a/redhat/configs/pending-common/generic/CONFIG_MT7921E +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_MT7921E: -# -# This adds support for MT7921E 802.11ax 2x2:2SS wireless devices. -# -# To compile this driver as a module, choose M here. -# -# Symbol: MT7921E [=n] -# Type : tristate -# Defined at drivers/net/wireless/mediatek/mt76/mt7921/Kconfig:2 -# Prompt: MediaTek MT7921E (PCIe) support -# Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && PCI [=y] -# Location: -# -> Device Drivers -# -> Network device support (NETDEVICES [=y]) -# -> Wireless LAN (WLAN [=y]) -# -> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y]) -# Selects: MT76_CONNAC_LIB [=n] && WANT_DEV_COREDUMP [=y] -# -# -# -# CONFIG_MT7921E is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/909

2 1

[OS-BUILD PATCH] [redhat] New configs in drivers/char
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in drivers/char Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_TCG_TIS_I2C_CR50: This is a driver for the Google cr50 I2C TPM interface which is a custom microcontroller and requires a custom i2c protocol interface to handle the limitations of the hardware. To compile this driver as a module, choose M here; the module will be called tcg_tis_i2c_cr50. Symbol: TCG_TIS_I2C_CR50 [=n] Type : tristate Defined at drivers/char/tpm/Kconfig:89 Prompt: TPM Interface Specification 2.0 Interface (I2C - CR50) Depends on: TCG_TPM [=y] && I2C [=y] Location: -> Device Drivers -> Character devices -> TPM Hardware Support (TCG_TPM [=y]) Selects: TCG_CR50 --- Cc: John Linville <linville(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_TCG_TIS_I2C_CR50 b/redhat/configs/common/generic/CONFIG_TCG_TIS_I2C_CR50 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_TCG_TIS_I2C_CR50 @@ -0,0 +1 @@ +# CONFIG_TCG_TIS_I2C_CR50 is not set diff a/redhat/configs/pending-common/generic/CONFIG_TCG_TIS_I2C_CR50 b/redhat/configs/pending-common/generic/CONFIG_TCG_TIS_I2C_CR50 --- a/redhat/configs/pending-common/generic/CONFIG_TCG_TIS_I2C_CR50 +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_TCG_TIS_I2C_CR50: -# -# This is a driver for the Google cr50 I2C TPM interface which is a -# custom microcontroller and requires a custom i2c protocol interface -# to handle the limitations of the hardware. To compile this driver -# as a module, choose M here; the module will be called tcg_tis_i2c_cr50. -# -# Symbol: TCG_TIS_I2C_CR50 [=n] -# Type : tristate -# Defined at drivers/char/tpm/Kconfig:89 -# Prompt: TPM Interface Specification 2.0 Interface (I2C - CR50) -# Depends on: TCG_TPM [=y] && I2C [=y] -# Location: -# -> Device Drivers -# -> Character devices -# -> TPM Hardware Support (TCG_TPM [=y]) -# Selects: TCG_CR50 -# -# -# -# CONFIG_TCG_TIS_I2C_CR50 is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/902

2 1

[OS-BUILD PATCH] [redhat] New configs in sound/core
by CKI Gitlab (via Email Bridge) 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> [redhat] New configs in sound/core Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_SND_JACK_INJECTION_DEBUG: This option can be used to enable or disable sound jack software injection. Say Y if you are debugging via jack injection interface. If unsure select "N". Symbol: SND_JACK_INJECTION_DEBUG [=n] Type : bool Defined at sound/core/Kconfig:190 Prompt: Sound jack injection interface via debugfs Depends on: SOUND [=m] && !UML && SND [=m] && SND_JACK [=y] && SND_DEBUG [=y] && DEBUG_FS [=y] Location: -> Device Drivers -> Sound card support (SOUND [=m]) -> Advanced Linux Sound Architecture (SND [=m]) -> Debug (SND_DEBUG [=y]) --- Cc: Jaroslav Kysela <jkysela(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> diff a/redhat/configs/common/generic/CONFIG_SND_JACK_INJECTION_DEBUG b/redhat/configs/common/generic/CONFIG_SND_JACK_INJECTION_DEBUG --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SND_JACK_INJECTION_DEBUG @@ -0,0 +1 @@ +# CONFIG_SND_JACK_INJECTION_DEBUG is not set diff a/redhat/configs/pending-common/generic/CONFIG_SND_JACK_INJECTION_DEBUG b/redhat/configs/pending-common/generic/CONFIG_SND_JACK_INJECTION_DEBUG --- a/redhat/configs/pending-common/generic/CONFIG_SND_JACK_INJECTION_DEBUG +++ /dev/null @@ -1,21 +0,0 @@ -# CONFIG_SND_JACK_INJECTION_DEBUG: -# -# This option can be used to enable or disable sound jack -# software injection. -# Say Y if you are debugging via jack injection interface. -# If unsure select "N". -# -# Symbol: SND_JACK_INJECTION_DEBUG [=n] -# Type : bool -# Defined at sound/core/Kconfig:190 -# Prompt: Sound jack injection interface via debugfs -# Depends on: SOUND [=m] && !UML && SND [=m] && SND_JACK [=y] && SND_DEBUG [=y] && DEBUG_FS [=y] -# Location: -# -> Device Drivers -# -> Sound card support (SOUND [=m]) -# -> Advanced Linux Sound Architecture (SND [=m]) -# -> Debug (SND_DEBUG [=y]) -# -# -# -# CONFIG_SND_JACK_INJECTION_DEBUG is not set -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/914

2 1

[OS-BUILD PATCH] [redhat] New configs in kernel/trace
by GitLab Bridge on behalf of redhat-patchlab 22 Feb '21

22 Feb '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_FTRACE_RECORD_RECURSION: All callbacks that attach to the function tracing have some sort of protection against recursion. Even though the protection exists, it adds overhead. This option will create a file in the tracefs file system called "recursed_functions" that will list the functions that triggered a recursion. This will add more overhead to cases that have recursion. If unsure, say N Symbol: FTRACE_RECORD_RECURSION [=n] Type : bool Defined at kernel/trace/Kconfig:737 Prompt: Record functions that recurse in function tracing Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && FUNCTION_TRACER [=y] Location: -> Kernel hacking -> Tracers (FTRACE [=y]) --- CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS: This will audit the time stamps on the ring buffer sub buffer to make sure that all the time deltas for the events on a sub buffer matches the current time stamp. This audit is performed for every event that is not interrupted, or interrupting another event. A check is also made when traversing sub buffers to make sure that all the deltas on the previous sub buffer do not add up to be greater than the current time stamp. NOTE: This adds significant overhead to recording of events, and should only be used to test the logic of the ring buffer. Do not use it on production systems. Only say Y if you understand what this does, and you still want it enabled. Otherwise say N Symbol: RING_BUFFER_VALIDATE_TIME_DELTAS [=n] Type : bool Defined at kernel/trace/Kconfig:846 Prompt: Verify ring buffer time stamp deltas Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && RING_BUFFER [=y] Location: -> Kernel hacking -> Tracers (FTRACE [=y]) --- Cc: Jerome Marchand <jmarchan(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../generic/CONFIG_FTRACE_RECORD_RECURSION | 1 + .../CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS | 1 + .../generic/CONFIG_FTRACE_RECORD_RECURSION | 24 --------------- .../CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS | 30 ------------------- 4 files changed, 2 insertions(+), 54 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_FTRACE_RECORD_RECURSION create mode 100644 redhat/configs/common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS delete mode 100644 redhat/configs/pending-common/generic/CONFIG_FTRACE_RECORD_RECURSION delete mode 100644 redhat/configs/pending-common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS diff --git a/redhat/configs/common/generic/CONFIG_FTRACE_RECORD_RECURSION b/redhat/configs/common/generic/CONFIG_FTRACE_RECORD_RECURSION new file mode 100644 index 000000000000..613dd9d01aef --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_FTRACE_RECORD_RECURSION @@ -0,0 +1 @@ +# CONFIG_FTRACE_RECORD_RECURSION is not set diff --git a/redhat/configs/common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS b/redhat/configs/common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS new file mode 100644 index 000000000000..062dee43468f --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS @@ -0,0 +1 @@ +# CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_FTRACE_RECORD_RECURSION b/redhat/configs/pending-common/generic/CONFIG_FTRACE_RECORD_RECURSION deleted file mode 100644 index d4b4d5a8a0da..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_FTRACE_RECORD_RECURSION +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_FTRACE_RECORD_RECURSION: -# -# All callbacks that attach to the function tracing have some sort -# of protection against recursion. Even though the protection exists, -# it adds overhead. This option will create a file in the tracefs -# file system called "recursed_functions" that will list the functions -# that triggered a recursion. -# -# This will add more overhead to cases that have recursion. -# -# If unsure, say N -# -# Symbol: FTRACE_RECORD_RECURSION [=n] -# Type : bool -# Defined at kernel/trace/Kconfig:737 -# Prompt: Record functions that recurse in function tracing -# Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && FUNCTION_TRACER [=y] -# Location: -# -> Kernel hacking -# -> Tracers (FTRACE [=y]) -# -# -# -# CONFIG_FTRACE_RECORD_RECURSION is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS b/redhat/configs/pending-common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS deleted file mode 100644 index 383636599d30..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS +++ /dev/null @@ -1,30 +0,0 @@ -# CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS: -# -# This will audit the time stamps on the ring buffer sub -# buffer to make sure that all the time deltas for the -# events on a sub buffer matches the current time stamp. -# This audit is performed for every event that is not -# interrupted, or interrupting another event. A check -# is also made when traversing sub buffers to make sure -# that all the deltas on the previous sub buffer do not -# add up to be greater than the current time stamp. -# -# NOTE: This adds significant overhead to recording of events, -# and should only be used to test the logic of the ring buffer. -# Do not use it on production systems. -# -# Only say Y if you understand what this does, and you -# still want it enabled. Otherwise say N -# -# Symbol: RING_BUFFER_VALIDATE_TIME_DELTAS [=n] -# Type : bool -# Defined at kernel/trace/Kconfig:846 -# Prompt: Verify ring buffer time stamp deltas -# Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && RING_BUFFER [=y] -# Location: -# -> Kernel hacking -# -> Tracers (FTRACE [=y]) -# -# -# -# CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS is not set -- GitLab

2 2

← Newer
1
...
7
8
9
10
11
12
13
...
16
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel February 2021