Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
1161705b
Commit
1161705b
authored
Mar 19, 2008
by
Ingo Molnar
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
x86: fill cpu to apicid and present map in mpparse, fix
Signed-off-by:
Ingo Molnar
<
mingo@elte.hu
>
parent
a6c422cc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
0 deletions
+6
-0
arch/x86/kernel/mpparse_32.c
arch/x86/kernel/mpparse_32.c
+6
-0
No files found.
arch/x86/kernel/mpparse_32.c
View file @
1161705b
...
...
@@ -75,6 +75,10 @@ unsigned disabled_cpus __cpuinitdata;
/* Bitmask of physically existing CPUs */
physid_mask_t
phys_cpu_present_map
;
#ifndef CONFIG_SMP
DEFINE_PER_CPU
(
u16
,
x86_bios_cpu_apicid
)
=
BAD_APICID
;
#endif
/*
* Intel MP BIOS table parsing routines:
*/
...
...
@@ -229,6 +233,7 @@ static void __cpuinit MP_processor_info (struct mpc_config_processor *m)
def_to_bigsmp
=
1
;
}
}
#ifdef CONFIG_SMP
/* are we being called early in kernel startup? */
if
(
x86_cpu_to_apicid_early_ptr
)
{
u16
*
cpu_to_apicid
=
x86_cpu_to_apicid_early_ptr
;
...
...
@@ -240,6 +245,7 @@ static void __cpuinit MP_processor_info (struct mpc_config_processor *m)
per_cpu
(
x86_cpu_to_apicid
,
cpu
)
=
m
->
mpc_apicid
;
per_cpu
(
x86_bios_cpu_apicid
,
cpu
)
=
m
->
mpc_apicid
;
}
#endif
cpu_set
(
cpu
,
cpu_present_map
);
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment