[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1359725603-20471-1-git-send-email-anish198519851985@gmail.com>
Date: Fri, 1 Feb 2013 19:03:23 +0530
From: anish kumar <anish198519851985@...il.com>
To: akpm@...ux-foundation.org, dzickus@...hat.com, tglx@...utronix.de,
mingo@...nel.org, chuansheng.liu@...el.com,
linux-kernel@...r.kernel.org
Cc: anish kumar <anish198519851985@...il.com>
Subject: [PATCH] [Watchdog][Trivial] Added comments to explain watchdog_disabled variable
From: anish kumar <anish198519851985@...il.com>
This watchdog_disabled flag is bit of cryptic.Howerver it's usefullnes is multifold.
Uses are:
1. Check if smpboot_register_percpu_thread function passed.
2. Makes sure that user enables and disables the watchdog in sequence
i.e. enable watchdog->disable watchdog->enable watchdog
Unlike enable watchdog->enable watchdog which is wrong.
Signed-off-by: anish kumar <anish198519851985@...il.com>
---
kernel/watchdog.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index 75a2ab3..6ef638b 100644
--- a/kernel/watchdog.c
+++ b/kernel/watchdog.c
@@ -155,6 +155,7 @@ void touch_all_softlockup_watchdogs(void)
for_each_online_cpu(cpu)
per_cpu(watchdog_touch_ts, cpu) = 0;
}
+EXPORT_SYMBOL(touch_all_softlockup_watchdogs);
#ifdef CONFIG_HARDLOCKUP_DETECTOR
void touch_nmi_watchdog(void)
--
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists