grilling troubled CPUs for fun and profit?
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · linux-os (Dick Johnson)
Quoted 3 lines · Andreas Mohr
while looking for loop places to apply
cpu_relax()to, I found the following gems:
Quoted 8 lines
Quoted 8 lines
arch/i386/kernel/crash.c/crash_nmi_callback():
/* Assume hlt works */ halt(); for(;;); return 1; }
This will result in the processor burning energy again after the first interrupt, won't it?
Quoted 5 lines
Quoted 5 lines
arch/i386/kernel/doublefault.c/doublefault_fn():
for (;;) /* nothing */; }
Quoted 7 lines
Quoted 4 lines
Let's assume that we have a less than moderate fan failure that causes the CPU to heat up beyond the critical limit...
That might result in - you guessed it - crashes or doublefaults. In which case we enter the corresponding handler and do... what?The double-fault is just a place-holder. The CPU will actually reset without even executing this (try it).
If it does reset, you don't need that fuctions (you can use anything), and if not, doing while(1) halt(); in both cases should DTRT even if the system is FUBAR, and it should be even smaller.
Quoted 6 lines
Quoted 2 lines
Exactly, we accelerate the CPUs happy march into bit heaven by letting it execute a busy-loop under a non-working fan.
You accelerate nothing. Bit heaven? A CPU without a fan will go into a cold, cold, shutdown, requiring a hardware reset to get it out of that latched, no internal clock running, mode.
Some CPU may do this, others will go via the random-generator mode into the self-deformation-mode instead.
Signature · 4 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF verbreiteten Lügen zu sabotieren. http://david.woodhou.se/why-not-spf.html
Quoted 12 lines · Bodo Eggert
Quoted 11 lines · linux-os (Dick Johnson)
Quoted 9 lines · Andreas Mohr
while looking for loop places to apply
cpu_relax()to, I found the following gems:arch/i386/kernel/crash.c/crash_nmi_callback():
/* Assume hlt works */ halt(); for(;;);
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
return 1; }This will result in the processor burning energy again after the first interrupt, won't it?
Interrupts are disabled here.
Dave
Signature · 1 line
http://www.codemonkey.org.uk