diff options
| author | Andreas Herrmann <[email protected]> | 2007-11-14 17:00:44 -0800 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2007-11-14 18:45:44 -0800 |
| commit | bae19fe033b0c5ed99b1ed27a4cce84625a24606 (patch) | |
| tree | fe8356f234bb4e8a1ab9edfb92bc9e8be0265b58 /tools/perf/scripts/python | |
| parent | 77f2878b4f78c0b29c4a2580665a446c77901152 (diff) | |
x86: don't call mce_create_device on CPU_UP_PREPARE
Fix regression introduced with d435d862baca3e25e5eec236762a43251b1e7ffc
("cpu hotplug: mce: fix cpu hotplug error handling").
A CPU which was not brought up during boot (using maxcpus and
additional_cpus parameters) couldn't be onlined anymore. For such a CPU it
seemed that MCE was not supported during CPU_UP_PREPARE-time which caused
mce_cpu_callback to return NOTIFY_BAD to notifier_call_chain. To fix this
we:
- call mce_create_device for CPU_ONLINE event (instead of CPU_UP_PREPARE),
- avoid mce_remove_device() for the CPU that is not correctly initialized
by mce_create_device() failure,
- make mce_cpu_callback always return NOTIFY_OK for CPU_ONLINE event.
Because CPU_ONLINE callback return value is always ignored.
[[email protected]: avoid mce_remove_device() for not initialized device]
[[email protected]: make mce_cpu_callback always return NOTIFY_OK]
Signed-off-by: Akinobu Mita <[email protected]>
Signed-off-by: Andreas Herrmann <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: Ingo Molnar <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions