1. 17 Jun, 2009 4 commits
    • Ingo Molnar's avatar
      Merge branch 'linus' into x86/urgent · cc4949e1
      Ingo Molnar authored
      Merge reason: pull in latest to fix a bug in it.
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      cc4949e1
    • H. Peter Anvin's avatar
      x86, boot: use .code16gcc instead of .code16 · 28b48688
      H. Peter Anvin authored
      Use .code16gcc to compile arch/x86/boot/bioscall.S rather than
      .code16, since some older versions of binutils can't generate 32-bit
      addressing expressions (67 prefixes) in .code16 mode, only in
      .code16gcc mode.
      Reported-by: default avatarTetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
      Signed-off-by: default avatarH. Peter Anvin <hpa@zytor.com>
      28b48688
    • Cliff Wickman's avatar
      x86: correct the conversion of EFI memory types · e2a71476
      Cliff Wickman authored
      This patch causes all the EFI_RESERVED_TYPE memory reservations to be recorded
      in the e820 table as type E820_RESERVED.
      
      (This patch replaces one called 'x86: vendor reserved memory type'.
       This version has been discussed a bit with Peter and Yinghai but not given
       a final opinion.)
      
      Without this patch EFI_RESERVED_TYPE memory reservations may be
      marked usable in the e820 table. There may be a collision between
      kernel use and some reserver's use of this memory.
      
      (An example use of this functionality is the UV system, which
       will access extremely large areas of memory with a memory engine
       that allows a user to address beyond the processor's range.  Such
       areas are reserved in the EFI table by the BIOS.
       Some loaders have a restricted number of entries possible in the e820 table,
       hence the need to record the reservations in the unrestricted EFI table.)
      
      The call to do_add_efi_memmap() is only made if "add_efi_memmap" is specified
      on the kernel command line.
      Signed-off-by: default avatarCliff Wickman <cpw@sgi.com>
      Signed-off-by: default avatarH. Peter Anvin <hpa@zytor.com>
      e2a71476
    • H. Peter Anvin's avatar
      x86: cap iomem_resource to addressable physical memory · 95ee14e4
      H. Peter Anvin authored
      iomem_resource is by default initialized to -1, which means 64 bits of
      physical address space if 64-bit resources are enabled.  However, x86
      CPUs cannot address 64 bits of physical address space.  Thus, we want
      to cap the physical address space to what the union of all CPU can
      actually address.
      
      Without this patch, we may end up assigning inaccessible values to
      uninitialized 64-bit PCI memory resources.
      Signed-off-by: default avatarH. Peter Anvin <hpa@zytor.com>
      Cc: Matthew Wilcox <matthew@wil.cx>
      Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
      Cc: Martin Mares <mj@ucw.cz>
      Cc: stable@kernel.org
      95ee14e4
  2. 16 Jun, 2009 36 commits