Displaying 6 results from an estimated 6 matches for "print_timestamp".
2007 Apr 18
2
[PATCH RFC] Change softlockup watchdog to ignore stolen time
...41fb9e70d72 kernel/softlockup.c
--- a/kernel/softlockup.c Thu Mar 22 16:25:15 2007 -0700
+++ b/kernel/softlockup.c Thu Mar 22 16:26:52 2007 -0700
@@ -17,9 +17,11 @@
static DEFINE_SPINLOCK(print_lock);
-static DEFINE_PER_CPU(unsigned long, touch_timestamp);
-static DEFINE_PER_CPU(unsigned long, print_timestamp);
+static DEFINE_PER_CPU(unsigned long long, touch_timestamp);
+static DEFINE_PER_CPU(unsigned long long, print_timestamp);
static DEFINE_PER_CPU(struct task_struct *, watchdog_task);
+
+#define SEC_NS (1000000000ull)
static int did_panic = 0;
@@ -37,7 +39,7 @@ static struct notifier_block pa...
2007 Apr 18
2
[PATCH RFC] Change softlockup watchdog to ignore stolen time
...41fb9e70d72 kernel/softlockup.c
--- a/kernel/softlockup.c Thu Mar 22 16:25:15 2007 -0700
+++ b/kernel/softlockup.c Thu Mar 22 16:26:52 2007 -0700
@@ -17,9 +17,11 @@
static DEFINE_SPINLOCK(print_lock);
-static DEFINE_PER_CPU(unsigned long, touch_timestamp);
-static DEFINE_PER_CPU(unsigned long, print_timestamp);
+static DEFINE_PER_CPU(unsigned long long, touch_timestamp);
+static DEFINE_PER_CPU(unsigned long long, print_timestamp);
static DEFINE_PER_CPU(struct task_struct *, watchdog_task);
+
+#define SEC_NS (1000000000ull)
static int did_panic = 0;
@@ -37,7 +39,7 @@ static struct notifier_block pa...
2007 Apr 18
5
[patch 0/4] Revised softlockup watchdog improvement patches
Hi Ingo,
This series of patches implements a number of improvements to the
softlockup watchdog and its users.
They are:
1. Make the watchdog ignore stolen time
When running under a hypervisor, the kernel may lose an arbitrary amount
of time as "stolen time". This may cause the softlockup watchdog to
trigger spruiously. Xen and VMI implement sched_clock() as measuring
unstolen time,
2007 Apr 18
5
[patch 0/4] Revised softlockup watchdog improvement patches
Hi Ingo,
This series of patches implements a number of improvements to the
softlockup watchdog and its users.
They are:
1. Make the watchdog ignore stolen time
When running under a hypervisor, the kernel may lose an arbitrary amount
of time as "stolen time". This may cause the softlockup watchdog to
trigger spruiously. Xen and VMI implement sched_clock() as measuring
unstolen time,
2007 Apr 18
2
[patch 0/2] softlockup watchdog improvements
Here's couple of patches to improve the softlockup watchdog.
The first changes the softlockup timer from using jiffies to sched_clock()
as a timebase. Xen and VMI implement sched_clock() as counting unstolen
time, so time stolen by the hypervisor won't cause the watchdog to bite.
The second adds per-cpu enable flags for the watchdog timer. This allows
the timer to be disabled when the
2007 Apr 18
2
[patch 0/2] softlockup watchdog improvements
Here's couple of patches to improve the softlockup watchdog.
The first changes the softlockup timer from using jiffies to sched_clock()
as a timebase. Xen and VMI implement sched_clock() as counting unstolen
time, so time stolen by the hypervisor won't cause the watchdog to bite.
The second adds per-cpu enable flags for the watchdog timer. This allows
the timer to be disabled when the