diff options
author | Thomas Renninger <trenn@suse.de> | 2007-05-02 19:27:22 +0200 |
---|---|---|
committer | Andi Kleen <andi@basil.nowhere.org> | 2007-05-02 19:27:22 +0200 |
commit | 35060b6a9a4e1c89bc6fbea61090e302dbc61847 (patch) | |
tree | 4f9ceb9b30e87799a011413523a332bc6bb262a8 /arch/x86_64/boot/setup.S | |
parent | a3193348d407baaa7aef79decfa0e9a7fef74a17 (diff) | |
download | kernel-crypto-35060b6a9a4e1c89bc6fbea61090e302dbc61847.tar.gz kernel-crypto-35060b6a9a4e1c89bc6fbea61090e302dbc61847.tar.xz kernel-crypto-35060b6a9a4e1c89bc6fbea61090e302dbc61847.zip |
[PATCH] i386: Don't delete cpu_devs data to identify different x86 types in late_initcall
In arch/i386/cpu/common.c there is:
cpu_devs[X86_VENDOR_INTEL]
cpu_devs[X86_VENDOR_CYRIX]
cpu_devs[X86_VENDOR_AMD]
...
They are all filled with data early.
The data (struct) got set to NULL for all, but Intel in different
late_initcall (exit_cpu_vendor) calls.
I don't see what sense this makes at all, maybe something that got
forgotten with the HOTPLUG_CPU extenstions?
Please check/review whether initdata, cpuinitdata is still ok and this
still works with HOTPLUG_CPU and without, it should...
Signed-off-by: Thomas Renninger <trenn@suse.de>
Signed-off-by: Andi Kleen <ak@suse.de>
Cc: davej@redhat.com
Diffstat (limited to 'arch/x86_64/boot/setup.S')
0 files changed, 0 insertions, 0 deletions