1. 21 Feb, 2003 3 commits
  2. 20 Feb, 2003 11 commits
    • Linus Torvalds's avatar
      3d34f2f7
    • Linus Torvalds's avatar
      Fix x86 "switch_to()" to properly set the previous task information, · e58d8e30
      Linus Torvalds authored
      which is needed to keep track of process usage counts correctly and
      efficiently.
      e58d8e30
    • Dave Hansen's avatar
      [PATCH] make io_apic.c use named initializers · 91e2be46
      Dave Hansen authored
      Bill Irwin was talking about hw_interrupt_type.set_affinity and kirq.
      When I went looking, I failed to find this initialization.
      
      Here are some nice, easy-to-find, named initializers.
      91e2be46
    • Andrew Morton's avatar
      [PATCH] Don't call mmdrop under a spinlock · 6fe3b423
      Andrew Morton authored
      We're calling mmdrop() under spin_lock_irq(&rq->lock).  But mmdrop
      calls vfree(), which calls smp_call_function().
      
      It is not legal to call smp_call_function() with irq's off.  Because
      another CPU may be running smp_call_function() against _this_ CPU, which
      deadlocks.
      
      So the patch arranges for mmdrop() to not be called under
      spin_lock_irq(&rq->lock).
      6fe3b423
    • Andrew Morton's avatar
      [PATCH] Keep interrupts enabled in exit path · 776969f0
      Andrew Morton authored
      We are leaving local interrupts disabled coming out of exit_notify().
      
      But we are about to call wait_task_inactive() which spins, waiting for
      another CPU to end a task.  If that CPU has issued smp_call_function() to
      this CPU, deadlock.
      
      So the patch enables interrupts again before returning from exit_notify().
      
      Also, exit_notify() returns with preemption disabled, so there is no
      need to perform another preempt_disable() in do_exit().
      776969f0
    • John Levon's avatar
      [PATCH] oprofile author needs to learn C · 3b6244e1
      John Levon authored
      Manifested as X profile appearing as /dev/mem ...
      3b6244e1
    • Duncan Sands's avatar
      [PATCH] USB speedtouch: take ref to USB device · 136537a2
      Duncan Sands authored
      udsl_atm_proc_read may be called after USB disconnect.
      136537a2
    • David Brownell's avatar
      [PATCH] USB: usbtest checks for in-order completions · 4f88b00d
      David Brownell authored
      This makes "test 10" verify that completions are returned in-order,
      resolving a FIXME.  OHCI and EHCI do, but UHCI doesn't. (*)  That
      simplified a cleanup of the queue fault tests to make it easier
      to handle optional faults (with one or more failure modes).
      
      It also returns a "lost subcase" that accidentally was not getting
      run.  And in a case of pure paranoia, the unlink tests handle the
      EBUSY return from an async urb unlink ... if that ever shows up I'd
      expect it to be on an SMP box.
      
      
      (*) I'd suspected as much given the first round of tests with UHCI;
           the diagnostics from "usbtest" made no sense otherwise.  This
           is just repeatable confirmation of the earlier bug report.  This
           could cause trouble in the usb_sg_*() I/O calls.
      
           In this case, "testusb -at10 -g4" reported that subcase 1 completed
           out of order (before subcase 0) ... without looking at details, I'd
           guess a list_add() vs list_add_tail() issue.
      
           Then after trying the queue cleanup code, I got diagnostics from
           uhci_destroy_urb_priv; then a kmalloc poisoning oops in uhci_irq,
           or "uhci_remove_pending_qhs+0x7c/0x1b0" in more detail.  Those
           looks to be the same "can't unlink from completions" errors that
           was also reported before in that code.
      
           Note that "testusb -at10" (like "testusb -at9") can be made to
           work with any USB device, using "usbtest" module options.
      4f88b00d
    • David Brownell's avatar
      [PATCH] USB: ohci-hcd fewer diagnostics · 135c5b70
      David Brownell authored
      This gets rid of some potentially scarey messages I've recently
      seen on disconnect, "bad hash" for a TD ... it's really a "no hash"
      case, and this prevents the message in some cases where that's
      not an issue.  Likely this is what Gary Gorgen noticed, but even
      he had a different problem, this message shouldn't always appear.
      
      It also slims down one other message, preventing it from appearing
      in the routine "protocol stall" case (and cluttering logfiles).
      135c5b70
    • David Brownell's avatar
      [PATCH] USB: ohci-hcd, more portable diagnostics · c9684e5e
      David Brownell authored
      This is the rest of the work to make the driver not care which
      version of the OS it's using, so the difference between the 2.5
      and 2.5 versions can just be a small patch with stuff that has
      a real need to be different.
      c9684e5e
    • David Brownell's avatar
      [PATCH] USB: sync with some 2.4 ohci fixes, prepare for backport · d3d118a8
      David Brownell authored
      The 2.5 version branched from 2.4.5 or so, and since then
      a couple hardware-specific tweaks were merged to 2.4; this
      teaches 2.5 about NatSemi SUPERIO and PA-RISC quirks.
      
      This also uses os/version neutral HCD calls to register the root
      hub and find the HCD's bus.  It also adds os/version neutral
      macros for its diagnostic macros.  Most of those changes have
      been split out separately, but the macros and a few uses of them
      weren't naturally splittable.
      
      Also a couple minor cleanups, like removing CVS ids, having
      only one copy of a routine used with the debug files, and
      getting rid of some inline #ifdefs.
      d3d118a8
  3. 19 Feb, 2003 26 commits