An error occurred fetching the project authors.
  1. 22 Aug, 2008 2 commits
  2. 15 Aug, 2008 2 commits
    • Marcin Slusarz's avatar
      x86: fix section mismatch warning - spp_getpage() · 8d6ea967
      Marcin Slusarz authored
      WARNING: vmlinux.o(.text+0x17a3e): Section mismatch in reference from the function set_pte_vaddr_pud() to the function .init.text:spp_getpage()
      The function set_pte_vaddr_pud() references
      the function __init spp_getpage().
      This is often because set_pte_vaddr_pud lacks a __init
      annotation or the annotation of spp_getpage is wrong.
      
      spp_getpage is called from __init (__init_extra_mapping) and
      non __init (set_pte_vaddr_pud) functions, so it can't be __init.
      Unfortunately it calls alloc_bootmem_pages which is __init,
      but does it only when bootmem allocator is available (after_bootmem == 0).
      
      So annotate it accordingly.
      Signed-off-by: default avatarMarcin Slusarz <marcin.slusarz@gmail.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      Cc: H. Peter Anvin <hpa@zytor.com>
      8d6ea967
    • Hugh Dickins's avatar
      x86: fix /proc/meminfo DirectMap · a06de630
      Hugh Dickins authored
      Do we actually want these DirectMap lines in the x86 /proc/meminfo?
      I can see they're interesting to CPA developers and TLB optimizers,
      but they don't fit its usual "where has all my memory gone?" usage.
      If they are to stay, here are some fixes.
      
      1. On x86_32 without PAE, they're not 2M but 4M pages: no need to
         mess with the internal enum, but show the right name to users.
      
      2. Many machines can never show anything but 0 for DirectMap1G,
         so suppress that line unless direct_gbpages are really enabled.
      
      3. The unit in /proc/meminfo is kB not number of pages: HugePages
         messed that up, but they're an example to regret not to follow.
      
      4. Once we use kB, it's easy to see that 1GB has gone missing (which
         explains why CONFIG_CPA_DEBUG=y soon wraps DirectMap2M negative):
         because head_64.S's level2_ident_pgt entries were not counted.
         My fix is not ideal, but works for more and for less than 1G,
         and avoids interfering with early bootup pagetable contortions.
      Signed-off-by: default avatarHugh Dickins <hugh@veritas.com>
      Cc: Andi Kleen <andi@firstfloor.org>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      a06de630
  3. 26 Jul, 2008 1 commit
  4. 18 Jul, 2008 1 commit
  5. 16 Jul, 2008 1 commit
  6. 13 Jul, 2008 1 commit
  7. 11 Jul, 2008 1 commit
  8. 10 Jul, 2008 1 commit
  9. 09 Jul, 2008 4 commits
  10. 08 Jul, 2008 18 commits
  11. 03 Jul, 2008 1 commit
  12. 26 Jun, 2008 1 commit
    • Daniel J Blueman's avatar
      x86: section/warning fixes · 0b1faeef
      Daniel J Blueman authored
      WARNING: arch/x86/mm/built-in.o(.text+0x3a1): Section mismatch in
      reference from the function set_pte_phys() to the function
      .init.text:spp_getpage()
      The function set_pte_phys() references
      the function __init spp_getpage().
      This is often because set_pte_phys lacks a __init
      annotation or the annotation of spp_getpage is wrong.
      
      arch/x86/mm/init_64.c: In function 'early_memtest':
      arch/x86/mm/init_64.c:520: warning: passing argument 2 of
      'find_e820_area_size' from incompatible pointer type
      Signed-off-by: default avatarDaniel J Blueman <daniel.blueman@gmail.com>
      Cc: "Linus Torvalds" <torvalds@linux-foundation.org>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      0b1faeef
  13. 20 Jun, 2008 2 commits
  14. 12 Jun, 2008 2 commits
  15. 04 Jun, 2008 2 commits