1. 03 Mar, 2004 1 commit
  2. 02 Mar, 2004 1 commit
  3. 04 Mar, 2004 1 commit
  4. 03 Mar, 2004 9 commits
  5. 02 Mar, 2004 16 commits
  6. 01 Mar, 2004 12 commits
    • Linus Torvalds's avatar
      Update x86 defconfig · 13d02fd8
      Linus Torvalds authored
      13d02fd8
    • Linus Torvalds's avatar
      Merge bk://kernel.bkbits.net/davem/net-2.6 · d038090e
      Linus Torvalds authored
      into ppc970.osdl.org:/home/torvalds/v2.5/linux
      d038090e
    • Linus Torvalds's avatar
      Merge bk://bk.linux1394.org/ieee1394-2.6 · f50d5e03
      Linus Torvalds authored
      into ppc970.osdl.org:/home/torvalds/v2.5/linux
      f50d5e03
    • Steve Kinneberg's avatar
    • Ben Collins's avatar
    • Andrew Morton's avatar
      [PATCH] oprofile: fix P4 HT msr sharing · 6a59dff3
      Andrew Morton authored
      From: Philippe Elie <phil.el@wanadoo.fr>
      
      When I debugged P4 ht oprofile a few month ago I noticed that but though it
      wasn't a problem...  The fix I propose is not completely clean.
      
      With P4 HT we split msr in two subset, one for each logical processor.  The
      msrs subset used in op_model_p4.c at save and setup point of view are
      distinct (*), it means we must serialize setup and save operation else a
      logical processor can save some msr value already setup by the other thread
      then when oprofile shutdown we restore wrong msrs values.
      
      Nobody noticed the problem because after restoring the msrs we call
      enable_lapic_nmi_watchdog() -> setup_p4_watchdog() wich clear all the msrs
      but it's a bit fragile.  If nmi watchdog is not enabled nothing bad occurs
      because the LVTPC remains disabled.
      
      (*) this is done in this way because it allows a lot of simplification in
      op_model_p4.c, yes it isn't clean but it's not fixable w/o rewriting 75% of
      op_model_p4.c and I think the code will be bigger and more complex.
      6a59dff3
    • Andrew Morton's avatar
      [PATCH] scripts/modpost warning · b7d83b8c
      Andrew Morton authored
      From: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
      
      I need the following patch to kill a warning (__endian() may be unused)
      when cross-compiling m68k kernels on an ia32 box.
      b7d83b8c
    • Andrew Morton's avatar
      [PATCH] m68k interrupt handling fix · 5d5c8930
      Andrew Morton authored
      From: Geert Uytterhoeven <geert@linux-m68k.org>
      
      The syscalls.h change broke the m68k interrupt management code, since
      sys_{request,free}_irq() are not syscalls, but routines to manage system
      (CPU) interrupts.
      5d5c8930
    • Andrew Morton's avatar
      [PATCH] swsusp: fix error handling in "not enough swap space" · f57a9b9f
      Andrew Morton authored
      From: Pavel Machek <pavel@ucw.cz>
      
      Without this, if there's not enough swapspace, suspend fails, but leaves
      devices suspended, leading to dead machine.
      f57a9b9f
    • Andrew Morton's avatar
      [PATCH] firmware loader: delay firmware hotplug event · f2825db1
      Andrew Morton authored
      From: Dmitry Torokhov <dtor_core@ameritech.net>
      
      Do not call hotplug until firmware class device is completely instantiated.
      f2825db1
    • Andrew Morton's avatar
      [PATCH] firmware loader: pin firmware module · 8813723a
      Andrew Morton authored
      From: Dmitry Torokhov <dtor_core@ameritech.net>
      
      We need to pin the firmware loader module until the last reference to the
      firmware class device is dropped and the class device is destroyed.
      8813723a
    • Andrew Morton's avatar
      [PATCH] convert pdflush to kthread · a4f10cfd
      Andrew Morton authored
      From: Keith Owens <kaos@sgi.com>
      
      New pdflush threads are launched on-demand by pdflush.
      
      It turns out that on some architectures (eg, ia64) a kernel thread inherits
      its parent's stack utilisation.  So after the thread-launches-a-thread
      cycle has progressed sufficiently far we run out of stack space and crash.
      
      Simple fix: convert pdflush to use kthreads.  All kthreads are parented by
      keventd so there is no stack windup as a result of pdflush launching
      pdflush.
      a4f10cfd