| commit | 8ae3a5a8dff2c92bd1087bb97c4a3bb61174303e | |
| author | Jan Beulich <jbeulich@novell.com> | |
| Thu, 21 Aug 2008 13:27:22 +0000 (21 14:27 +0100) | ||
| committer | Ingo Molnar <mingo@elte.hu> | |
| Fri, 22 Aug 2008 05:51:53 +0000 (22 07:51 +0200) | ||
| tree | ccf10f1382360d6d91e694da8d8ec4c1dd675367 | treesnapshot (tar.gz zip) |
| parent | 38cc1c3df77c1bb739a4766788eb9fa49f16ffdf | commitdiff |
x86: fix 1:1 mapping init on 64-bit (memory hotplug case)
While I don't have a hotplug capable system at hand, I think two issues need
fixing:
- pud_phys (in kernel_physical_ampping_init()) would remain uninitialized in
the after_bootmem case
- the locking done just around phys_pmd_{init,update}() would leave out pgd
updates, and it was needlessly covering code portions that do allocations
(perhaps using a more friendly gfp value in alloc_low_page() would then be
possible)
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
While I don't have a hotplug capable system at hand, I think two issues need
fixing:
- pud_phys (in kernel_physical_ampping_init()) would remain uninitialized in
the after_bootmem case
- the locking done just around phys_pmd_{init,update}() would leave out pgd
updates, and it was needlessly covering code portions that do allocations
(perhaps using a more friendly gfp value in alloc_low_page() would then be
possible)
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
| arch/x86/mm/init_64.c | diffblobblamehistory |