1. 26 9月, 2006 1 次提交
  2. 02 9月, 2006 1 次提交
  3. 04 7月, 2006 2 次提交
  4. 03 7月, 2006 2 次提交
  5. 02 7月, 2006 2 次提交
  6. 30 6月, 2006 13 次提交
  7. 23 6月, 2006 1 次提交
    • J
      [PATCH] adjust handle_IRR_event() return type · 908dcecd
      Jan Beulich 提交于
      Correct the return type of handle_IRQ_event() (inconsistency noticed during
      Xen development), and remove redundant declarations.  The return type
      adjustment required breaking out the definition of irqreturn_t into a
      separate header, in order to satisfy current include order dependencies.
      Signed-off-by: NJan Beulich <jbeulich@novell.com>
      
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: Ian Molton <spyro@f2s.com>
      Cc: Mikael Starvik <starvik@axis.com>
      Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
      Cc: Hirokazu Takata <takata.hirokazu@renesas.com>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: William Lee Irwin III <wli@holomorphy.com>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Miles Bader <uclinux-v850@lsi.nec.co.jp>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      908dcecd
  8. 28 9月, 2005 1 次提交
  9. 08 9月, 2005 1 次提交
  10. 29 6月, 2005 1 次提交
    • A
      [PATCH] irqpoll · 200803df
      Alan Cox 提交于
      Anyone reporting a stuck IRQ should try these options.  Its effectiveness
      varies we've found in the Fedora case.  Quite a few systems with misdescribed
      IRQ routing just work when you use irqpoll.  It also fixes up the VIA systems
      although thats now fixed with the VIA quirk (which we could just make default
      as its what Redmond OS does but Linus didn't like it historically).
      
      A small number of systems have jammed IRQ sources or misdescribes that cause
      an IRQ that we have no handler registered anywhere for.  In those cases it
      doesn't help.
      Signed-off-by: NAlan Cox <number6@the-village.bc.nu>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      200803df
  11. 29 5月, 2005 1 次提交
    • J
      [PATCH] drop note_interrupt() for per-CPU for proper scaling · b60c1f6f
      John Hawkes 提交于
      The "unhandled interrupts" catcher, note_interrupt(), increments a global
      desc->irq_count and grossly damages scaling of very large systems, e.g.,
      >192p ia64 Altix, because of this highly contented cacheline, especially
      for timer interrupts.  384p is severely crippled, and 512p is unuseable.
      
      All calls to note_interrupt() can be disabled by booting with "noirqdebug",
      but this disables the useful interrupt checking for all interrupts.
      
      I propose eliminating note_interrupt() for all per-CPU interrupts.  This
      was the behavior of linux-2.6.10 and earlier, but in 2.6.11 a code
      restructuring added a call to note_interrupt() for per-CPU interrupts.
      Besides, note_interrupt() is a bit racy for concurrent CPU calls anyway, as
      the desc->irq_count++ increment isn't atomic (which, if done, would make
      scaling even worse).
      Signed-off-by: NJohn Hawkes <hawkes@sgi.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      b60c1f6f
  12. 17 5月, 2005 1 次提交
    • Z
      [PATCH] spurious interrupt fix · 4f167fb4
      Zhang, Yanmin 提交于
      On my IA64 machine, after kernel 2.6.12-rc3 boots, an edge-triggered
      interrupt (IRQ 46) keeps triggered over and over again.  There is no IRQ 46
      interrupt action handler.  It has lots of impact on performance.
      
      Kernel 2.6.10 and its prior versions have no the problem.  Basically,
      kernel 2.6.10 will mask the spurious edge interrupt if the interrupt is
      triggered for the second time and its status includes
      IRQ_DISABLE|IRQ_PENDING.
      
      Originally, IA64 kernel has its own specific _irq_desc definitions in file
      arch/ia64/kernel/irq.c.  The definition initiates _irq_desc[irq].status to
      IRQ_DISABLE.  Since kernel 2.6.11, it was moved to architecture independent
      codes, i.e.  kernel/irq/handle.c, but kernel/irq/handle.c initiates
      _irq_desc[irq].status to 0 instead of IRQ_DISABLE.
      Signed-off-by: NZhang Yanmin <yanmin.zhang@intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4f167fb4
  13. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4