1. 03 Aug, 2005 3 commits
    • Haren Myneni's avatar
      [PATCH] Xmon bug fix for soft-reset · 5cb4cc0d
      Haren Myneni authored
      For soft reset during system hang, got an error "CPU did not take
      control" for some CPUs even though they responded to soft-reset (called
      SystemReset, die and called debugger - xmon).   First these CPUs entered
      into xmon by IPI callback and then got a soft-reset exception and
      re-entered into xmon again. The first CPU which re-entered into xmon got
      the output lock and made into xmon successfully without unlocking.
      Hence, the next CPU(s) which re-entered into xmon try to acquire a lock
      (get_output_lock). Therefore, we can not view state of those CPU(s).
      
      [This is a simple, very low risk, obvious fix for an obvious bug, and
      should go into 2.6.13.  -- paulus]
      Signed-off-by: default avatarHaren Myneni <hbabu@us.ibm.com>
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      5cb4cc0d
    • Ivan Kokshaysky's avatar
      [PATCH] ACPI: increase PCIBIOS_MIN_IO on x86 · 0b2bfb4e
      Ivan Kokshaysky authored
      We have increased PCIBIOS_MIN_IO to 0x4000, but still want
      motherboard resources to be allocated properly. So we need
      to state 0x1000 (according to the comment) limit explicitely.
      Signed-off-by: default avatarIvan Kokshaysky <ink@jurassic.park.msu.ru>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      0b2bfb4e
    • Ivan Kokshaysky's avatar
      [PATCH] increase PCIBIOS_MIN_IO on x86 · 71db63ac
      Ivan Kokshaysky authored
      There is a number of x86 laptops that have some non-PCI IO ports
      in the 0x1000-0x1fff range, and it's quite hard to control the correct
      order of resource allocation between PCI and other subsystems controlling
      these ports. Especially with modular kernel.
      
      So just increase PCIBIOS_MIN_IO to 0x4000 to prevent any new PCI
      resource allocations in the problematic range (this limitation must
      apply _only_ to the root bus resources - see Linus' change in
      pci_bus_alloc_resource).  As PCIBIOS_MIN_IO and PCIBIOS_MIN_CARDBUS_IO
      are the same now on i386 and x86-64, we can remove the latter.
      Signed-off-by: default avatarIvan Kokshaysky <ink@jurassic.park.msu.ru>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      71db63ac
  2. 02 Aug, 2005 35 commits
  3. 01 Aug, 2005 2 commits
    • Linus Torvalds's avatar
      Revert ACPI interrupt resume changes · 697a2d63
      Linus Torvalds authored
      If there are devices that use interrupts over a suspend event, ACPI must
      restore the PCI interrupt links on resume.  Anything else breaks any
      device that hasn't been converted to the new (dubious) PM rules.
      
      Drivers that need the irq free/re-aquire sequence can be done one by one
      independently of this one.
      697a2d63
    • Linus Torvalds's avatar
      Fix get_user_pages() race for write access · 4ceb5db9
      Linus Torvalds authored
      There's no real guarantee that handle_mm_fault() will always be able to
      break a COW situation - if an update from another thread ends up
      modifying the page table some way, handle_mm_fault() may end up
      requiring us to re-try the operation.
      
      That's normally fine, but get_user_pages() ended up re-trying it as a
      read, and thus a write access could in theory end up losing the dirty
      bit or be done on a page that had not been properly COW'ed.
      
      This makes get_user_pages() always retry write accesses as write
      accesses by making "follow_page()" require that a writable follow has
      the dirty bit set.  That simplifies the code and solves the race: if the
      COW break fails for some reason, we'll just loop around and try again.
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      4ceb5db9