diff options
| author | Ivan Vecera <ivecera@redhat.com> | 2008-11-11 14:33:44 +0100 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-11-11 14:50:02 +0100 |
| commit | d3ec5cae0921611ceae06464ef6291012dd9849f (patch) | |
| tree | 81a84f184f9047b12895bbd91c1e8b1ff2e076f0 /drivers/rtc | |
| parent | 3ad4f597058301c97f362e500a32f63f5c950a45 (diff) | |
| download | kernel_samsung_smdk4412-d3ec5cae0921611ceae06464ef6291012dd9849f.tar.gz kernel_samsung_smdk4412-d3ec5cae0921611ceae06464ef6291012dd9849f.tar.bz2 kernel_samsung_smdk4412-d3ec5cae0921611ceae06464ef6291012dd9849f.zip | |
x86: call machine_shutdown and stop all CPUs in native_machine_halt
Impact: really halt all CPUs on halt
Function machine_halt (resp. native_machine_halt) is empty for x86
architectures. When command 'halt -f' is invoked, the message "System
halted." is displayed but this is not really true because all CPUs are
still running.
There are also similar inconsistencies for other arches (some uses
power-off for halt or forever-loop with IRQs enabled/disabled).
IMO there should be used the same approach for all architectures OR
what does the message "System halted" really mean?
This patch fixes it for x86.
Signed-off-by: Ivan Vecera <ivecera@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'drivers/rtc')
0 files changed, 0 insertions, 0 deletions