The param "irqflood_suppress" is helpful for capture kernel to survive irq
flood.

Signed-off-by: Pingfan Liu <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Jisheng Zhang <[email protected]>
Cc: Andrew Morton <[email protected]>
Cc: "Guilherme G. Piccoli" <[email protected]>
Cc: Petr Mladek <[email protected]>
Cc: Marc Zyngier <[email protected]>
Cc: Linus Walleij <[email protected]>
Cc: afzal mohammed <[email protected]>
Cc: Lina Iyer <[email protected]>
Cc: "Gustavo A. R. Silva" <[email protected]>
Cc: Maulik Shah <[email protected]>
Cc: Al Viro <[email protected]>
Cc: Jonathan Corbet <[email protected]>
Cc: Pawan Gupta <[email protected]>
Cc: Mike Kravetz <[email protected]>
Cc: Oliver Neukum <[email protected]>
To: [email protected]
Cc: [email protected]
Cc: [email protected]
---
 Documentation/admin-guide/kernel-parameters.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/admin-guide/kernel-parameters.txt 
b/Documentation/admin-guide/kernel-parameters.txt
index a106874..0a25a05 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -2009,6 +2009,9 @@
                        for it. Also check all handlers each timer
                        interrupt. Intended to get systems with badly broken
                        firmware running.
+       irqflood_suppress       [HW]
+                       When a irq fully occupies a cpu in a long time, 
suppressing
+                       it to make kernel move on. It is useful in the capture 
kernel.
 
        isapnp=         [ISAPNP]
                        Format: <RDP>,<reset>,<pci_scan>,<verbosity>
-- 
2.7.5

Reply via email to