On Mon, Jan 14, 2013 at 4:30 PM, Colin Cross wrote:
> On Mon, Jan 14, 2013 at 4:25 PM, Andrew Morton
> wrote:
>> On Mon, 14 Jan 2013 16:19:23 -0800
>> Colin Cross wrote:
>>
>>> >> +static void watchdog_check_hardlockup_other_cpu(void)
>>> >> +{
>>> >> + unsigned int next_cpu;
>>> >> +
>>>
On Mon, Jan 14, 2013 at 4:30 PM, Colin Cross ccr...@android.com wrote:
On Mon, Jan 14, 2013 at 4:25 PM, Andrew Morton
a...@linux-foundation.org wrote:
On Mon, 14 Jan 2013 16:19:23 -0800
Colin Cross ccr...@android.com wrote:
+static void watchdog_check_hardlockup_other_cpu(void)
+{
+
On Tue, Jan 15, 2013 at 01:13:10AM +0100, Frederic Weisbecker wrote:
> 2013/1/11 Colin Cross :
> > Emulate NMIs on systems where they are not available by using timer
> > interrupts on other cpus. Each cpu will use its softlockup hrtimer
> > to check that the next cpu is processing hrtimer
On Tue, Jan 15, 2013 at 01:13:10AM +0100, Frederic Weisbecker wrote:
2013/1/11 Colin Cross ccr...@android.com:
Emulate NMIs on systems where they are not available by using timer
interrupts on other cpus. Each cpu will use its softlockup hrtimer
to check that the next cpu is processing
On Mon, Jan 14, 2013 at 6:48 PM, Frederic Weisbecker wrote:
> 2013/1/15 Colin Cross :
>> On Mon, Jan 14, 2013 at 4:25 PM, Frederic Weisbecker
>> wrote:
>>> 2013/1/15 Colin Cross :
On Mon, Jan 14, 2013 at 4:13 PM, Frederic Weisbecker
wrote:
> I believe this is pretty much what
2013/1/15 Colin Cross :
> On Mon, Jan 14, 2013 at 4:25 PM, Frederic Weisbecker
> wrote:
>> 2013/1/15 Colin Cross :
>>> On Mon, Jan 14, 2013 at 4:13 PM, Frederic Weisbecker
>>> wrote:
I believe this is pretty much what the RCU stall detector does
already: checks for other CPUs being
On Mon, Jan 14, 2013 at 4:25 PM, Frederic Weisbecker wrote:
> 2013/1/15 Colin Cross :
>> On Mon, Jan 14, 2013 at 4:13 PM, Frederic Weisbecker
>> wrote:
>>> I believe this is pretty much what the RCU stall detector does
>>> already: checks for other CPUs being responsive. The only difference
>>>
On Mon, Jan 14, 2013 at 4:19 PM, Colin Cross wrote:
> On Mon, Jan 14, 2013 at 3:49 PM, Andrew Morton
> wrote:
>> On Fri, 11 Jan 2013 13:51:48 -0800
>> Colin Cross wrote:
>>
>>> Emulate NMIs on systems where they are not available by using timer
>>> interrupts on other cpus. Each cpu will use
On Mon, Jan 14, 2013 at 4:25 PM, Andrew Morton
wrote:
> On Mon, 14 Jan 2013 16:19:23 -0800
> Colin Cross wrote:
>
>> >> +static void watchdog_check_hardlockup_other_cpu(void)
>> >> +{
>> >> + unsigned int next_cpu;
>> >> +
>> >> + /*
>> >> + * Test for hardlockups every 3 samples.
2013/1/15 Colin Cross :
> On Mon, Jan 14, 2013 at 4:13 PM, Frederic Weisbecker
> wrote:
>> I believe this is pretty much what the RCU stall detector does
>> already: checks for other CPUs being responsive. The only difference
>> is on how it checks that. For RCU it's about checking for CPUs
>>
On Mon, 14 Jan 2013 16:19:23 -0800
Colin Cross wrote:
> >> +static void watchdog_check_hardlockup_other_cpu(void)
> >> +{
> >> + unsigned int next_cpu;
> >> +
> >> + /*
> >> + * Test for hardlockups every 3 samples. The sample period is
> >> + * watchdog_thresh * 2 / 5, so 3
On Mon, Jan 14, 2013 at 4:13 PM, Frederic Weisbecker wrote:
> 2013/1/11 Colin Cross :
>> Emulate NMIs on systems where they are not available by using timer
>> interrupts on other cpus. Each cpu will use its softlockup hrtimer
>> to check that the next cpu is processing hrtimer interrupts by
>>
On Mon, Jan 14, 2013 at 3:49 PM, Andrew Morton
wrote:
> On Fri, 11 Jan 2013 13:51:48 -0800
> Colin Cross wrote:
>
>> Emulate NMIs on systems where they are not available by using timer
>> interrupts on other cpus. Each cpu will use its softlockup hrtimer
>> to check that the next cpu is
2013/1/11 Colin Cross :
> Emulate NMIs on systems where they are not available by using timer
> interrupts on other cpus. Each cpu will use its softlockup hrtimer
> to check that the next cpu is processing hrtimer interrupts by
> verifying that a counter is increasing.
>
> This patch is useful on
On Fri, 11 Jan 2013 13:51:48 -0800
Colin Cross wrote:
> Emulate NMIs on systems where they are not available by using timer
> interrupts on other cpus. Each cpu will use its softlockup hrtimer
> to check that the next cpu is processing hrtimer interrupts by
> verifying that a counter is
On Fri, 11 Jan 2013 13:51:48 -0800
Colin Cross ccr...@android.com wrote:
Emulate NMIs on systems where they are not available by using timer
interrupts on other cpus. Each cpu will use its softlockup hrtimer
to check that the next cpu is processing hrtimer interrupts by
verifying that a
2013/1/11 Colin Cross ccr...@android.com:
Emulate NMIs on systems where they are not available by using timer
interrupts on other cpus. Each cpu will use its softlockup hrtimer
to check that the next cpu is processing hrtimer interrupts by
verifying that a counter is increasing.
This patch
On Mon, Jan 14, 2013 at 3:49 PM, Andrew Morton
a...@linux-foundation.org wrote:
On Fri, 11 Jan 2013 13:51:48 -0800
Colin Cross ccr...@android.com wrote:
Emulate NMIs on systems where they are not available by using timer
interrupts on other cpus. Each cpu will use its softlockup hrtimer
to
On Mon, Jan 14, 2013 at 4:13 PM, Frederic Weisbecker fweis...@gmail.com wrote:
2013/1/11 Colin Cross ccr...@android.com:
Emulate NMIs on systems where they are not available by using timer
interrupts on other cpus. Each cpu will use its softlockup hrtimer
to check that the next cpu is
On Mon, 14 Jan 2013 16:19:23 -0800
Colin Cross ccr...@android.com wrote:
+static void watchdog_check_hardlockup_other_cpu(void)
+{
+ unsigned int next_cpu;
+
+ /*
+ * Test for hardlockups every 3 samples. The sample period is
+ * watchdog_thresh * 2 / 5, so 3
2013/1/15 Colin Cross ccr...@android.com:
On Mon, Jan 14, 2013 at 4:13 PM, Frederic Weisbecker fweis...@gmail.com
wrote:
I believe this is pretty much what the RCU stall detector does
already: checks for other CPUs being responsive. The only difference
is on how it checks that. For RCU it's
On Mon, Jan 14, 2013 at 4:25 PM, Andrew Morton
a...@linux-foundation.org wrote:
On Mon, 14 Jan 2013 16:19:23 -0800
Colin Cross ccr...@android.com wrote:
+static void watchdog_check_hardlockup_other_cpu(void)
+{
+ unsigned int next_cpu;
+
+ /*
+ * Test for hardlockups
On Mon, Jan 14, 2013 at 4:19 PM, Colin Cross ccr...@android.com wrote:
On Mon, Jan 14, 2013 at 3:49 PM, Andrew Morton
a...@linux-foundation.org wrote:
On Fri, 11 Jan 2013 13:51:48 -0800
Colin Cross ccr...@android.com wrote:
Emulate NMIs on systems where they are not available by using timer
On Mon, Jan 14, 2013 at 4:25 PM, Frederic Weisbecker fweis...@gmail.com wrote:
2013/1/15 Colin Cross ccr...@android.com:
On Mon, Jan 14, 2013 at 4:13 PM, Frederic Weisbecker fweis...@gmail.com
wrote:
I believe this is pretty much what the RCU stall detector does
already: checks for other
2013/1/15 Colin Cross ccr...@android.com:
On Mon, Jan 14, 2013 at 4:25 PM, Frederic Weisbecker fweis...@gmail.com
wrote:
2013/1/15 Colin Cross ccr...@android.com:
On Mon, Jan 14, 2013 at 4:13 PM, Frederic Weisbecker fweis...@gmail.com
wrote:
I believe this is pretty much what the RCU stall
On Mon, Jan 14, 2013 at 6:48 PM, Frederic Weisbecker fweis...@gmail.com wrote:
2013/1/15 Colin Cross ccr...@android.com:
On Mon, Jan 14, 2013 at 4:25 PM, Frederic Weisbecker fweis...@gmail.com
wrote:
2013/1/15 Colin Cross ccr...@android.com:
On Mon, Jan 14, 2013 at 4:13 PM, Frederic
Emulate NMIs on systems where they are not available by using timer
interrupts on other cpus. Each cpu will use its softlockup hrtimer
to check that the next cpu is processing hrtimer interrupts by
verifying that a counter is increasing.
This patch is useful on systems where the hardlockup
Emulate NMIs on systems where they are not available by using timer
interrupts on other cpus. Each cpu will use its softlockup hrtimer
to check that the next cpu is processing hrtimer interrupts by
verifying that a counter is increasing.
This patch is useful on systems where the hardlockup
28 matches
Mail list logo
