1. 09 12月, 2006 1 次提交
    • J
      [PATCH] Generic BUG for i386 · 91768d6c
      Jeremy Fitzhardinge 提交于
      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: NJeremy 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: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      91768d6c
  2. 07 12月, 2006 6 次提交
  3. 04 10月, 2006 1 次提交
    • M
      Attack of "the the"s in arch · 4b3f686d
      Matt LaPlante 提交于
      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: NAdrian Bunk <bunk@stusta.de>
      4b3f686d
  4. 02 10月, 2006 1 次提交
    • A
      [PATCH] Kprobes: Make kprobe modules more portable · 3a872d89
      Ananth N Mavinakayanahalli 提交于
      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: NAnanth N Mavinakayanahalli <ananth@in.ibm.com>
      Signed-off-by: NPrasanna S Panchamukhi <prasanna@in.ibm.com>
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      3a872d89
  5. 27 9月, 2006 3 次提交
  6. 26 9月, 2006 5 次提交
  7. 28 8月, 2006 1 次提交
  8. 01 8月, 2006 1 次提交
  9. 04 7月, 2006 2 次提交
  10. 01 7月, 2006 1 次提交
  11. 30 6月, 2006 2 次提交
  12. 28 6月, 2006 3 次提交
    • I
      [PATCH] vdso: randomize the i386 vDSO by moving it into a vma · e6e5494c
      Ingo Molnar 提交于
      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: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NArjan 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: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e6e5494c
    • J
      [PATCH] fix subarchitecture breakage with CONFIG_SCHED_SMT · 96c52749
      James Bottomley 提交于
      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: NJames Bottomley <James.Bottomley@SteelEye.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      96c52749
    • G
      [PATCH] 64bit Resource: finally enable 64bit resource sizes · 6550e07f
      Greg Kroah-Hartman 提交于
      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: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      6550e07f
  13. 27 6月, 2006 5 次提交
  14. 23 6月, 2006 2 次提交
  15. 16 5月, 2006 1 次提交
  16. 28 4月, 2006 2 次提交
    • A
      [PATCH] Mark VMSPLIT EMBEDDED · 9539d4e7
      Andi Kleen 提交于
      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: NAndi Kleen <ak@suse.de>
      Cc: Adrian Bunk <bunk@stusta.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9539d4e7
    • A
      [PATCH] enable X86_PC for HOTPLUG_CPU · 35076bdf
      Ashok Raj 提交于
      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: NAshok Raj <ashok.raj@intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      35076bdf
  17. 11 4月, 2006 3 次提交