1. 11 Feb, 2007 1 commit
    • Christoph Lameter's avatar
      [PATCH] Set CONFIG_ZONE_DMA for arches with GENERIC_ISA_DMA · 5ac6da66
      Christoph Lameter authored
      
      
      As Andi pointed out: CONFIG_GENERIC_ISA_DMA only disables the ISA DMA
      channel management.  Other functionality may still expect GFP_DMA to
      provide memory below 16M.  So we need to make sure that CONFIG_ZONE_DMA is
      set independent of CONFIG_GENERIC_ISA_DMA.  Undo the modifications to
      mm/Kconfig where we made ZONE_DMA dependent on GENERIC_ISA_DMA and set
      theses explicitly in each arches Kconfig.
      
      Reviews must occur for each arch in order to determine if ZONE_DMA can be
      switched off.  It can only be switched off if we know that all devices
      supported by a platform are capable of performing DMA transfers to all of
      memory (Some arches already support this: uml, avr32, sh sh64, parisc and
      IA64/Altix).
      
      In order to switch ZONE_DMA off conditionally, one would have to establish
      a scheme by which one can assure that no drivers are enabled that are only
      capable of doing I/O to a part of memory, or one needs to provide an
      alternate means of performing an allocation from a specific range of memory
      (like provided by alloc_pages_range()) and insure that all drivers use that
      call.  In that case the arches alloc_dma_coherent() may need to be modified
      to call alloc_pages_range() instead of relying on GFP_DMA.
      Signed-off-by: default avatarChristoph Lameter <clameter@sgi.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      5ac6da66
  2. 06 Jan, 2007 1 commit
    • Vivek Goyal's avatar
      [PATCH] i386: Restore CONFIG_PHYSICAL_START option · dd0ec16f
      Vivek Goyal authored
      
      
      o Relocatable bzImage support had got rid of CONFIG_PHYSICAL_START option
        thinking that now this option is not required as people can build a
        second kernel as relocatable and load it anywhere. So need of compiling
        the kernel for a custom address was gone. But Magnus uses vmlinux images
        for second kernel in Xen environment and he wants to continue to use
        it.
      
      o Restoring the CONFIG_PHYSICAL_START option for the time being. I think
        down the line we can get rid of it.
      Signed-off-by: default avatarVivek Goyal <vgoyal@in.ibm.com>
      Cc: "Eric W. Biederman" <ebiederm@xmission.com>
      Cc: Andi Kleen <ak@suse.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      dd0ec16f
  3. 09 Dec, 2006 1 commit
    • Randy Dunlap's avatar
      [PATCH] x86-64: no paravirt for X86_VOYAGER or X86_VISWS · f0f32fcc
      Randy Dunlap authored
      
      
      Since Voyager and Visual WS already define ARCH_SETUP,
      it looks like PARAVIRT shouldn't be offered for them.
      
      In file included from arch/i386/kernel/setup.c:63:
      include/asm-i386/mach-visws/setup_arch.h:8:1: warning: "ARCH_SETUP" redefin=
      ed
      In file included from include/asm/msr.h:5,
                       from include/asm/processor.h:17,
                       from include/asm/thread_info.h:16,
                       from include/linux/thread_info.h:21,
                       from include/linux/preempt.h:9,
                       from include/linux/spinlock.h:49,
                       from include/linux/capability.h:45,
                       from include/linux/sched.h:46,
                       from arch/i386/kernel/setup.c:26:
      include/asm/paravirt.h:163:1: warning: this is the location of the previous=
       definition
      In file included from arch/i386/kernel/setup.c:63:
      include/asm-i386/mach-visws/setup_arch.h:8:1: warning: "ARCH_SETUP" redefin=
      ed
      In file included from include/asm/msr.h:5,
                       from include/asm/processor.h:17,
                       from include/asm/thread_info.h:16,
                       from include/linux/thread_info.h:21,
                       from include/linux/preempt.h:9,
                       from include/linux/spinlock.h:49,
                       from include/linux/capability.h:45,
                       from include/linux/sched.h:46,
                       from arch/i386/kernel/setup.c:26:
      include/asm/paravirt.h:163:1: warning: this is the location of the previous=
       definition
      Signed-off-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
      f0f32fcc
  4. 08 Dec, 2006 1 commit
    • Jeremy Fitzhardinge's avatar
      [PATCH] Generic BUG for i386 · 91768d6c
      Jeremy Fitzhardinge authored
      
      
      This makes i386 use the generic BUG machinery.  There are no functional
      changes from the old i386 implementation.
      
      The main advantage in using the generic BUG machinery for i386 is that the
      inlined overhead of BUG is just the ud2a instruction; the file+line(+function)
      information are no longer inlined into the instruction stream.  This reduces
      cache pollution, and makes disassembly work properly.
      Signed-off-by: default avatarJeremy Fitzhardinge <jeremy@goop.org>
      Cc: Andi Kleen <ak@muc.de>
      Cc: Hugh Dickens <hugh@veritas.com>
      Cc: Michael Ellerman <michael@ellerman.id.au>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Rusty Russell <rusty@rustcorp.com.au>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      91768d6c
  5. 06 Dec, 2006 6 commits
  6. 03 Oct, 2006 1 commit
    • Matt LaPlante's avatar
      Attack of "the the"s in arch · 4b3f686d
      Matt LaPlante authored
      
      
      The patch below corrects multiple occurances of "the the"
      typos across several files, both in source comments and KConfig files.
      There is no actual code changed, only text.  Note this only affects the /arch
      directory, and I believe I could find many more elsewhere. :)
      Signed-off-by: default avatarAdrian Bunk <bunk@stusta.de>
      4b3f686d
  7. 02 Oct, 2006 1 commit
    • Ananth N Mavinakayanahalli's avatar
      [PATCH] Kprobes: Make kprobe modules more portable · 3a872d89
      Ananth N Mavinakayanahalli authored
      
      
      In an effort to make kprobe modules more portable, here is a patch that:
      
      o Introduces the "symbol_name" field to struct kprobe.
        The symbol->address resolution now happens in the kernel in an
        architecture agnostic manner. 64-bit powerpc users no longer have
        to specify the ".symbols"
      o Introduces the "offset" field to struct kprobe to allow a user to
        specify an offset into a symbol.
      o The legacy mechanism of specifying the kprobe.addr is still supported.
        However, if both the kprobe.addr and kprobe.symbol_name are specified,
        probe registration fails with an -EINVAL.
      o The symbol resolution code uses kallsyms_lookup_name(). So
        CONFIG_KPROBES now depends on CONFIG_KALLSYMS
      o Apparantly kprobe modules were the only legitimate out-of-tree user of
        the kallsyms_lookup_name() EXPORT. Now that the symbol resolution
        happens in-kernel, remove the EXPORT as suggested by Christoph Hellwig
      o Modify tcp_probe.c that uses the kprobe interface so as to make it
        work on multiple platforms (in its earlier form, the code wouldn't
        work, say, on powerpc)
      Signed-off-by: default avatarAnanth N Mavinakayanahalli <ananth@in.ibm.com>
      Signed-off-by: default avatarPrasanna S Panchamukhi <prasanna@in.ibm.com>
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      3a872d89
  8. 27 Sep, 2006 3 commits
  9. 26 Sep, 2006 5 commits
  10. 27 Aug, 2006 1 commit
  11. 31 Jul, 2006 1 commit
  12. 03 Jul, 2006 2 commits
  13. 30 Jun, 2006 1 commit
  14. 29 Jun, 2006 2 commits
  15. 27 Jun, 2006 3 commits
    • Ingo Molnar's avatar
      [PATCH] vdso: randomize the i386 vDSO by moving it into a vma · e6e5494c
      Ingo Molnar authored
      
      
      Move the i386 VDSO down into a vma and thus randomize it.
      
      Besides the security implications, this feature also helps debuggers, which
      can COW a vma-backed VDSO just like a normal DSO and can thus do
      single-stepping and other debugging features.
      
      It's good for hypervisors (Xen, VMWare) too, which typically live in the same
      high-mapped address space as the VDSO, hence whenever the VDSO is used, they
      get lots of guest pagefaults and have to fix such guest accesses up - which
      slows things down instead of speeding things up (the primary purpose of the
      VDSO).
      
      There's a new CONFIG_COMPAT_VDSO (default=y) option, which provides support
      for older glibcs that still rely on a prelinked high-mapped VDSO.  Newer
      distributions (using glibc 2.3.3 or later) can turn this option off.  Turning
      it off is also recommended for security reasons: attackers cannot use the
      predictable high-mapped VDSO page as syscall trampoline anymore.
      
      There is a new vdso=[0|1] boot option as well, and a runtime
      /proc/sys/vm/vdso_enabled sysctl switch, that allows the VDSO to be turned
      on/off.
      
      (This version of the VDSO-randomization patch also has working ELF
      coredumping, the previous patch crashed in the coredumping code.)
      
      This code is a combined work of the exec-shield VDSO randomization
      code and Gerd Hoffmann's hypervisor-centric VDSO patch. Rusty Russell
      started this patch and i completed it.
      
      [akpm@osdl.org: cleanups]
      [akpm@osdl.org: compile fix]
      [akpm@osdl.org: compile fix 2]
      [akpm@osdl.org: compile fix 3]
      [akpm@osdl.org: revernt MAXMEM change]
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      Signed-off-by: default avatarArjan van de Ven <arjan@infradead.org>
      Cc: Gerd Hoffmann <kraxel@suse.de>
      Cc: Rusty Russell <rusty@rustcorp.com.au>
      Cc: Zachary Amsden <zach@vmware.com>
      Cc: Andi Kleen <ak@muc.de>
      Cc: Jan Beulich <jbeulich@novell.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      e6e5494c
    • James Bottomley's avatar
      [PATCH] fix subarchitecture breakage with CONFIG_SCHED_SMT · 96c52749
      James Bottomley authored
      Commit 1e9f28fa
      
       ("[PATCH] sched: new
      sched domain for representing multi-core") incorrectly made SCHED_SMT
      and some of the structures it uses dependent on SMP.
      
      However, this is wrong, the structures are only defined if X86_HT, so
      SCHED_SMT has to depend on that as well.
      
      The patch broke voyager, since it doesn't provide any of the multi-core
      or hyperthreading structures.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      96c52749
    • Greg Kroah-Hartman's avatar
      [PATCH] 64bit Resource: finally enable 64bit resource sizes · 6550e07f
      Greg Kroah-Hartman authored
      
      
      Introduce the Kconfig entry and actually switch to a 64bit value, if
      wanted, for resource_size_t.
      
      Based on a patch series originally from Vivek Goyal <vgoyal@in.ibm.com>
      
      Cc: Vivek Goyal <vgoyal@in.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      6550e07f
  16. 26 Jun, 2006 5 commits
  17. 23 Jun, 2006 2 commits
  18. 15 May, 2006 1 commit
  19. 28 Apr, 2006 2 commits
    • Andi Kleen's avatar
      [PATCH] Mark VMSPLIT EMBEDDED · 9539d4e7
      Andi Kleen authored
      
      
      Running abnormal VM splits causes weird problems - people can set non-standard
      splits by accident, then lots of time gets wasted diagnosing it - see the long
      "[stable] 2.6.16.6 breaks java...  sort of" email thread.
      
      So we need to make this option harder to set.  Use CONFIG_EMBEDDED for this.
      
      CONFIG_EMBEDDED isn't really the right thing to use, but there's nothing else
      obvious and avoiding these problems is more important than Kconfig purity.
      Signed-off-by: default avatarAndi Kleen <ak@suse.de>
      Cc: Adrian Bunk <bunk@stusta.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      9539d4e7
    • Ashok Raj's avatar
      [PATCH] enable X86_PC for HOTPLUG_CPU · 35076bdf
      Ashok Raj authored
      
      
      CPU_HOTPLUG has race conditions when we use broadcast mode IPI.
      
      - First we introduced no_broadcast option
          (see include/asm-i386/mach-default/mach_ipi.h)
      
      - x86_64 solved it by using physical flat mode (same as bigsmp on i386)
        since this will not use broadcast shortcuts for IPI.
      
      - We switched to use bigsmp on i386 so that we can have same handling as
        x86_64, but apparently this caused an error message, if kernel was
        compiled without X86_GENERICARCH, X86_BIGSMP.  The message "You have >8
        CPUS..." which was bogus and misleading, and only indicated one of the
        above ARCH wasnt selected.
      
      So we do not switch to automatic bigsmp for HOTPLUG_CPU support in i386
      until the other related config dependencies for SMP_SUSPEND etc can be done
      right.
      Signed-off-by: default avatarAshok Raj <ashok.raj@intel.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      35076bdf