[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by GitLab Bridge on behalf of redhat-patchlab
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_HARDLOCKUP_DETECTOR:
Say Y here to enable the kernel to act as a watchdog to detect
hard lockups.
Hardlockups are bugs that cause the CPU to loop in kernel mode
for more than 10 seconds, without letting other interrupts have a
chance to run. The current stack trace is displayed upon detection
and the system will stay locked up.
Symbol: HARDLOCKUP_DETECTOR [=n]
Type : bool
Defined at lib/Kconfig.debug:1000
Prompt: Detect Hard Lockups
Depends on: DEBUG_KERNEL [=y] && !S390 && (HAVE_HARDLOCKUP_DETECTOR_PERF [=y] || HAVE_HARDLOCKUP_DETECTOR_ARCH [=n])
Location:
-> Kernel hacking
-> Debug Oops, Lockups and Hangs
Selects: LOCKUP_DETECTOR [=y] && HARDLOCKUP_DETECTOR_PERF [=n] && HARDLOCKUP_DETECTOR_ARCH
---
Cc: Prarit Bhargava <prarit(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_HARDLOCKUP_DETECTOR | 1 +
.../generic/CONFIG_HARDLOCKUP_DETECTOR | 23 -------------------
2 files changed, 1 insertion(+), 23 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_HARDLOCKUP_DETECTOR
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_HARDLOCKUP_DETECTOR
diff --git a/redhat/configs/common/generic/CONFIG_HARDLOCKUP_DETECTOR b/redhat/configs/common/generic/CONFIG_HARDLOCKUP_DETECTOR
new file mode 100644
index 000000000000..32d4a56dd961
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_HARDLOCKUP_DETECTOR
@@ -0,0 +1 @@
+# CONFIG_HARDLOCKUP_DETECTOR is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_HARDLOCKUP_DETECTOR b/redhat/configs/pending-common/generic/CONFIG_HARDLOCKUP_DETECTOR
deleted file mode 100644
index cd74a33e67ea..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_HARDLOCKUP_DETECTOR
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_HARDLOCKUP_DETECTOR:
-#
-# Say Y here to enable the kernel to act as a watchdog to detect
-# hard lockups.
-#
-# Hardlockups are bugs that cause the CPU to loop in kernel mode
-# for more than 10 seconds, without letting other interrupts have a
-# chance to run. The current stack trace is displayed upon detection
-# and the system will stay locked up.
-#
-# Symbol: HARDLOCKUP_DETECTOR [=n]
-# Type : bool
-# Defined at lib/Kconfig.debug:1000
-# Prompt: Detect Hard Lockups
-# Depends on: DEBUG_KERNEL [=y] && !S390 && (HAVE_HARDLOCKUP_DETECTOR_PERF [=y] || HAVE_HARDLOCKUP_DETECTOR_ARCH [=n])
-# Location:
-# -> Kernel hacking
-# -> Debug Oops, Lockups and Hangs
-# Selects: LOCKUP_DETECTOR [=y] && HARDLOCKUP_DETECTOR_PERF [=n] && HARDLOCKUP_DETECTOR_ARCH
-#
-#
-#
-# CONFIG_HARDLOCKUP_DETECTOR is not set
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in drivers/md
by GitLab Bridge on behalf of redhat-patchlab
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_DM_MULTIPATH_IOA:
This path selector selects the path based on the CPU the IO is
executed on and the CPU to path mapping setup at path addition time.
If unsure, say N.
Symbol: DM_MULTIPATH_IOA [=n]
Type : tristate
Defined at drivers/md/Kconfig:466
Prompt: I/O Path Selector based on CPU submission
Depends on: MD [=y] && DM_MULTIPATH [=m]
Location:
-> Device Drivers
-> Multiple devices driver support (RAID and LVM) (MD [=y])
-> Device mapper support (BLK_DEV_DM [=m])
-> Multipath target (DM_MULTIPATH [=m])
---
Cc: Nigel Croxon <ncroxon(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_DM_MULTIPATH_IOA | 1 +
.../generic/CONFIG_DM_MULTIPATH_IOA | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_DM_MULTIPATH_IOA
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DM_MULTIPATH_IOA
diff --git a/redhat/configs/common/generic/CONFIG_DM_MULTIPATH_IOA b/redhat/configs/common/generic/CONFIG_DM_MULTIPATH_IOA
new file mode 100644
index 000000000000..9dbcf92fa81e
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DM_MULTIPATH_IOA
@@ -0,0 +1 @@
+# CONFIG_DM_MULTIPATH_IOA is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DM_MULTIPATH_IOA b/redhat/configs/pending-common/generic/CONFIG_DM_MULTIPATH_IOA
deleted file mode 100644
index 83a1a727f1bd..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DM_MULTIPATH_IOA
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_DM_MULTIPATH_IOA:
-#
-# This path selector selects the path based on the CPU the IO is
-# executed on and the CPU to path mapping setup at path addition time.
-#
-# If unsure, say N.
-#
-# Symbol: DM_MULTIPATH_IOA [=n]
-# Type : tristate
-# Defined at drivers/md/Kconfig:466
-# Prompt: I/O Path Selector based on CPU submission
-# Depends on: MD [=y] && DM_MULTIPATH [=m]
-# Location:
-# -> Device Drivers
-# -> Multiple devices driver support (RAID and LVM) (MD [=y])
-# -> Device mapper support (BLK_DEV_DM [=m])
-# -> Multipath target (DM_MULTIPATH [=m])
-#
-#
-#
-# CONFIG_DM_MULTIPATH_IOA is not set
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in drivers/nvme
by GitLab Bridge on behalf of jeremycline
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_NVME_TARGET_PASSTHRU:
This enables target side NVMe passthru controller support for the
NVMe Over Fabrics protocol. It allows for hosts to manage and
directly access an actual NVMe controller residing on the target
side, incuding executing Vendor Unique Commands.
If unsure, say N.
Symbol: NVME_TARGET_PASSTHRU [=n]
Type : bool
Defined at drivers/nvme/target/Kconfig:19
Prompt: NVMe Target Passthrough support
Depends on: NVME_TARGET [=m] && (NVME_CORE [=m]=y || NVME_CORE [=m]=NVME_TARGET [=m])
Location:
-> Device Drivers
-> NVME Support
-> NVMe Target support (NVME_TARGET [=m])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../generic/CONFIG_NVME_TARGET_PASSTHRU | 1 +
.../generic/CONFIG_NVME_TARGET_PASSTHRU | 22 -------------------
2 files changed, 1 insertion(+), 22 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU
diff --git a/redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU b/redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU
new file mode 100644
index 000000000000..12bf02e23a41
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU
@@ -0,0 +1 @@
+# CONFIG_NVME_TARGET_PASSTHRU is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU b/redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU
deleted file mode 100644
index 2795e2bb3e5e..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_NVME_TARGET_PASSTHRU:
-#
-# This enables target side NVMe passthru controller support for the
-# NVMe Over Fabrics protocol. It allows for hosts to manage and
-# directly access an actual NVMe controller residing on the target
-# side, incuding executing Vendor Unique Commands.
-#
-# If unsure, say N.
-#
-# Symbol: NVME_TARGET_PASSTHRU [=n]
-# Type : bool
-# Defined at drivers/nvme/target/Kconfig:19
-# Prompt: NVMe Target Passthrough support
-# Depends on: NVME_TARGET [=m] && (NVME_CORE [=m]=y || NVME_CORE [=m]=NVME_TARGET [=m])
-# Location:
-# -> Device Drivers
-# -> NVME Support
-# -> NVMe Target support (NVME_TARGET [=m])
-#
-#
-#
-# CONFIG_NVME_TARGET_PASSTHRU is not set
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] common: enable RTC_SYSTOHC to supplement
update_persistent_clock64
by GitLab Bridge on behalf of pbrobinson
From: Peter Robinson <pbrobinson(a)gmail.com>
We already enable RTC_HCTOSYS in common config, this is the inverse
for syncing NTP to HW RTCs, and seems slightly better/preferred on
non x86-style CMOS RTCa than update_persistent_clock.
Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com>
---
redhat/configs/common/generic/CONFIG_RTC_SYSTOHC | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/redhat/configs/common/generic/CONFIG_RTC_SYSTOHC b/redhat/configs/common/generic/CONFIG_RTC_SYSTOHC
index 03ebe734a152..f3581c76b8c6 100644
--- a/redhat/configs/common/generic/CONFIG_RTC_SYSTOHC
+++ b/redhat/configs/common/generic/CONFIG_RTC_SYSTOHC
@@ -1 +1 @@
-# CONFIG_RTC_SYSTOHC is not set
+CONFIG_RTC_SYSTOHC=y
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] efi: The EFI_VARS is legacy and now x86 only
by GitLab Bridge on behalf of pbrobinson
From: Peter Robinson <pbrobinson(a)gmail.com>
As of upstream commit 963fabf the EFI_VARS option is set to x86
only as it's long been deprecated pre !intel support and is due to
be removed so it now does nothing on arm platforms.
Fedora actually disabled this on x86 too, I do wonder if it's
worth considering disabling it in ark platforms too?
Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com>
Cc: Mark Salter <msalter(a)redhat.com>
Cc: Al Stone <ahs3(a)redhat.com>
---
redhat/configs/ark/generic/arm/aarch64/CONFIG_EFI_VARS | 1 -
redhat/configs/fedora/generic/arm/CONFIG_EFI_VARS | 1 -
2 files changed, 2 deletions(-)
delete mode 100644 redhat/configs/ark/generic/arm/aarch64/CONFIG_EFI_VARS
delete mode 100644 redhat/configs/fedora/generic/arm/CONFIG_EFI_VARS
diff --git a/redhat/configs/ark/generic/arm/aarch64/CONFIG_EFI_VARS b/redhat/configs/ark/generic/arm/aarch64/CONFIG_EFI_VARS
deleted file mode 100644
index b9206d9f457a..000000000000
--- a/redhat/configs/ark/generic/arm/aarch64/CONFIG_EFI_VARS
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_EFI_VARS=y
diff --git a/redhat/configs/fedora/generic/arm/CONFIG_EFI_VARS b/redhat/configs/fedora/generic/arm/CONFIG_EFI_VARS
deleted file mode 100644
index b9206d9f457a..000000000000
--- a/redhat/configs/fedora/generic/arm/CONFIG_EFI_VARS
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_EFI_VARS=y
--
GitLab
3 years, 1 month
[OS-BUILD PATCH 0/7] Move all x86 legacy input options to that
architecture
by GitLab Bridge on behalf of pbrobinson
From: pbrobinson on gitlab.com
None of the non x86 architectures support PS2, AT keyboards, i8042
controllers and related bits. This cleans up a bunch of those options as
well as syncing some of the Fedora options on non x86 to be the same as
ARK by moving the ARK bits to generic.
Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com>
3 years, 1 month
[OS-BUILD PATCH] Disable bluetooth highspeed by default
by GitLab Bridge on behalf of pbrobinson
From: Peter Robinson <pbrobinson(a)gmail.com>
Upstream has disabled BT_HS by disabled because it wasn't widely adopted.
It's also been referenced upstream by BleedingTooth vulnerability:
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa...
Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com>
---
redhat/configs/common/generic/CONFIG_BT_HS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/redhat/configs/common/generic/CONFIG_BT_HS b/redhat/configs/common/generic/CONFIG_BT_HS
index e0151a2e9e0d..fbbd6bcf002f 100644
--- a/redhat/configs/common/generic/CONFIG_BT_HS
+++ b/redhat/configs/common/generic/CONFIG_BT_HS
@@ -1 +1 @@
-CONFIG_BT_HS=y
+# CONFIG_BT_HS is not set
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline
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_CMDLINE:
On some platforms, there is currently no way for the boot loader to
pass arguments to the kernel. For these platforms, you can supply
some command-line options at build time by entering them here. In
most cases you will need to specify the root device here.
Symbol: CMDLINE [=]
Type : string
Defined at arch/powerpc/Kconfig:882
Prompt: Initial kernel command string
Location:
-> Kernel options
---
CONFIG_PPC_QUEUED_SPINLOCKS:
Say Y here to use queued spinlocks which give better scalability and
fairness on large SMP and NUMA systems without harming single threaded
performance.
This option is currently experimental, the code is more complex and
less tested so it defaults to "N" for the moment.
If unsure, say "N".
Symbol: PPC_QUEUED_SPINLOCKS [=n]
Type : bool
Defined at arch/powerpc/Kconfig:497
Prompt: Queued spinlocks
Depends on: SMP [=y]
Location:
-> Kernel options
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_CMDLINE | 1 +
.../generic/CONFIG_PPC_QUEUED_SPINLOCKS | 1 +
.../pending-common/generic/CONFIG_CMDLINE | 17 --------------
.../generic/CONFIG_PPC_QUEUED_SPINLOCKS | 22 -------------------
4 files changed, 2 insertions(+), 39 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_CMDLINE
create mode 100644 redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CMDLINE
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS
diff --git a/redhat/configs/common/generic/CONFIG_CMDLINE b/redhat/configs/common/generic/CONFIG_CMDLINE
new file mode 100644
index 000000000000..f3083e1e5200
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CMDLINE
@@ -0,0 +1 @@
+CONFIG_CMDLINE=""
diff --git a/redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS b/redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS
new file mode 100644
index 000000000000..f1f7e79da5c3
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PPC_QUEUED_SPINLOCKS
@@ -0,0 +1 @@
+# CONFIG_PPC_QUEUED_SPINLOCKS is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_CMDLINE b/redhat/configs/pending-common/generic/CONFIG_CMDLINE
deleted file mode 100644
index 10611732c5eb..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CMDLINE
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_CMDLINE:
-#
-# On some platforms, there is currently no way for the boot loader to
-# pass arguments to the kernel. For these platforms, you can supply
-# some command-line options at build time by entering them here. In
-# most cases you will need to specify the root device here.
-#
-# Symbol: CMDLINE [=]
-# Type : string
-# Defined at arch/powerpc/Kconfig:882
-# Prompt: Initial kernel command string
-# Location:
-# -> Kernel options
-#
-#
-#
-CONFIG_CMDLINE=""
diff --git a/redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS b/redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS
deleted file mode 100644
index 90ecdc77e696..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PPC_QUEUED_SPINLOCKS
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_PPC_QUEUED_SPINLOCKS:
-#
-# Say Y here to use queued spinlocks which give better scalability and
-# fairness on large SMP and NUMA systems without harming single threaded
-# performance.
-#
-# This option is currently experimental, the code is more complex and
-# less tested so it defaults to "N" for the moment.
-#
-# If unsure, say "N".
-#
-# Symbol: PPC_QUEUED_SPINLOCKS [=n]
-# Type : bool
-# Defined at arch/powerpc/Kconfig:497
-# Prompt: Queued spinlocks
-# Depends on: SMP [=y]
-# Location:
-# -> Kernel options
-#
-#
-#
-# CONFIG_PPC_QUEUED_SPINLOCKS is not set
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in kernel/trace
by GitLab Bridge on behalf of redhat-patchlab
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
3 years, 2 months
[OS-BUILD PATCH] [redhat] New configs in drivers/net/ethernet/chelsio
by GitLab Bridge on behalf of jeremycline
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_CHELSIO_INLINE_CRYPTO:
Enable support for inline crypto.
Allows enable/disable from list of inline crypto drivers.
Symbol: CHELSIO_INLINE_CRYPTO [=y]
Type : bool
Defined at drivers/net/ethernet/chelsio/inline_crypto/Kconfig:6
Prompt: Chelsio Inline Crypto support
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_CHELSIO [=y] && CHELSIO_T4 [=m]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> Chelsio devices (NET_VENDOR_CHELSIO [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../generic/CONFIG_CHELSIO_INLINE_CRYPTO | 1 +
.../generic/CONFIG_CHELSIO_INLINE_CRYPTO | 19 -------------------
2 files changed, 1 insertion(+), 19 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
diff --git a/redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO b/redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
new file mode 100644
index 000000000000..bd32df3059f2
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
@@ -0,0 +1 @@
+CONFIG_CHELSIO_INLINE_CRYPTO=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO b/redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
deleted file mode 100644
index 95b39e771a2a..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CHELSIO_INLINE_CRYPTO
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_CHELSIO_INLINE_CRYPTO:
-#
-# Enable support for inline crypto.
-# Allows enable/disable from list of inline crypto drivers.
-#
-# Symbol: CHELSIO_INLINE_CRYPTO [=y]
-# Type : bool
-# Defined at drivers/net/ethernet/chelsio/inline_crypto/Kconfig:6
-# Prompt: Chelsio Inline Crypto support
-# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_CHELSIO [=y] && CHELSIO_T4 [=m]
-# Location:
-# -> Device Drivers
-# -> Network device support (NETDEVICES [=y])
-# -> Ethernet driver support (ETHERNET [=y])
-# -> Chelsio devices (NET_VENDOR_CHELSIO [=y])
-#
-#
-#
-CONFIG_CHELSIO_INLINE_CRYPTO=y
--
GitLab
3 years, 2 months