Merge tag 'x86-apic-2024-03-10' of git://git.kernel.org/pub/scm/linux/kernel/git...

[linux-2.6-microblaze.git] / Documentation / admin-guide / kernel-parameters.txt

diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 94314d0..8a081ac 100644 (file)
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -680,12 +680,6 @@
                        loops can be debugged more effectively on production
                        systems.
 
-       clocksource.max_cswd_read_retries= [KNL]
-                       Number of clocksource_watchdog() retries due to
-                       external delays before the clock will be marked
-                       unstable.  Defaults to two retries, that is,
-                       three attempts to read the clock under test.
-
        clocksource.verify_n_cpus= [KNL]
                        Limit the number of CPUs checked for clocksources
                        marked with CLOCK_SOURCE_VERIFY_PERCPU that
@@ -1101,15 +1095,6 @@
                        Disable TLBIE instruction. Currently does not work
                        with KVM, with HASH MMU, or with coherent accelerators.
 
-       disable_cpu_apicid= [X86,APIC,SMP]
-                       Format: <int>
-                       The number of initial APIC ID for the
-                       corresponding CPU to be disabled at boot,
-                       mostly used for the kdump 2nd kernel to
-                       disable BSP to wake up multiple CPUs without
-                       causing system reset or hang due to sending
-                       INIT from AP to BSP.
-
        disable_ddw     [PPC/PSERIES,EARLY]
                        Disable Dynamic DMA Window support. Use this
                        to workaround buggy firmware.
@@ -7244,6 +7229,15 @@
                        threshold repeatedly. They are likely good
                        candidates for using WQ_UNBOUND workqueues instead.
 
+       workqueue.cpu_intensive_warning_thresh=<uint>
+                       If CONFIG_WQ_CPU_INTENSIVE_REPORT is set, the kernel
+                       will report the work functions which violate the
+                       intensive_threshold_us repeatedly. In order to prevent
+                       spurious warnings, start printing only after a work
+                       function has violated this threshold number of times.
+
+                       The default is 4 times. 0 disables the warning.
+
        workqueue.power_efficient
                        Per-cpu workqueues are generally preferred because
                        they show better performance thanks to cache