1. 01 5月, 2008 2 次提交
    • S
      x86: use defconfigs from x86/configs/* · b9b39bfb
      Sam Ravnborg 提交于
      Daniel Drake <dsd@gentoo.org> reported:
      
      In 2.6.23, if you unpacked a kernel source tarball and then
      ran "make menuconfig" you'd be presented with this message:
          # using defaults found in arch/i386/defconfig
      
      and the default options would be set.
      
      The same thing in 2.6.24 does not give you any "using defaults" message, and
      the default config options within menuconfig are rather blank (e.g. no PCI
      support). You can work around this by explicitly running "make defconfig"
      before menuconfig, but it would be nice to have the behaviour the way it was
      for 2.6.23 (and the way it still is for other archs).
      
      Fixed by adding a x86 specific defconfig list to Kconfig.
      
      Fixes: http://bugzilla.kernel.org/show_bug.cgi?id=10470
      Tested-by: dsd@gentoo.org
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      b9b39bfb
    • I
      x86 VISWS: build fix · 3e8f7e35
      Ingo Molnar 提交于
      the 'reboot_force' flag is a notion that non-PC subarchitectures do
      not have.
      
      also, unify the X86_BIOS_REBOOT option between 32-bit and 64-bit
      and get rid of a few unnecessary Kconfig and Makefile complications
      that way.
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      3e8f7e35
  2. 29 4月, 2008 2 次提交
  3. 28 4月, 2008 2 次提交
  4. 27 4月, 2008 7 次提交
  5. 26 4月, 2008 2 次提交
  6. 25 4月, 2008 1 次提交
  7. 20 4月, 2008 2 次提交
  8. 18 4月, 2008 1 次提交
  9. 17 4月, 2008 11 次提交
  10. 13 3月, 2008 1 次提交
  11. 12 3月, 2008 1 次提交
    • T
      x86: remove quicklists · 985a34bd
      Thomas Gleixner 提交于
      quicklists cause a serious memory leak on 32-bit x86,
      as documented at:
      
        http://bugzilla.kernel.org/show_bug.cgi?id=9991
      
      the reason is that the quicklist pool is a special-purpose
      cache that grows out of proportion. It is not accounted for
      anywhere and users have no way to even realize that it's
      the quicklists that are causing RAM usage spikes. It was
      supposed to be a relatively small pool, but as demonstrated
      by KOSAKI Motohiro, they can grow as large as:
      
        Quicklists:    1194304 kB
      
      given how much trouble this code has caused historically,
      and given that Andrew objected to its introduction on x86
      (years ago), the best option at this point is to remove them.
      
      [ any performance benefits of caching constructed pgds should
        be implemented in a more generic way (possibly within the page
        allocator), while still allowing constructed pages to be
        allocated by other workloads. ]
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      985a34bd
  12. 05 3月, 2008 1 次提交
  13. 04 3月, 2008 1 次提交
  14. 23 2月, 2008 1 次提交
  15. 15 2月, 2008 1 次提交
  16. 09 2月, 2008 3 次提交
  17. 08 2月, 2008 1 次提交
    • C
      SLUB: Alternate fast paths using cmpxchg_local · 1f84260c
      Christoph Lameter 提交于
      Provide an alternate implementation of the SLUB fast paths for alloc
      and free using cmpxchg_local. The cmpxchg_local fast path is selected
      for arches that have CONFIG_FAST_CMPXCHG_LOCAL set. An arch should only
      set CONFIG_FAST_CMPXCHG_LOCAL if the cmpxchg_local is faster than an
      interrupt enable/disable sequence. This is known to be true for both
      x86 platforms so set FAST_CMPXCHG_LOCAL for both arches.
      
      Currently another requirement for the fastpath is that the kernel is
      compiled without preemption. The restriction will go away with the
      introduction of a new per cpu allocator and new per cpu operations.
      
      The advantages of a cmpxchg_local based fast path are:
      
      1. Potentially lower cycle count (30%-60% faster)
      
      2. There is no need to disable and enable interrupts on the fast path.
         Currently interrupts have to be disabled and enabled on every
         slab operation. This is likely avoiding a significant percentage
         of interrupt off / on sequences in the kernel.
      
      3. The disposal of freed slabs can occur with interrupts enabled.
      
      The alternate path is realized using #ifdef's. Several attempts to do the
      same with macros and inline functions resulted in a mess (in particular due
      to the strange way that local_interrupt_save() handles its argument and due
      to the need to define macros/functions that sometimes disable interrupts
      and sometimes do something else).
      
      [clameter: Stripped preempt bits and disabled fastpath if preempt is enabled]
      Signed-off-by: NChristoph Lameter <clameter@sgi.com>
      Reviewed-by: NPekka Enberg <penberg@cs.helsinki.fi>
      Cc: <linux-arch@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      1f84260c