1. 09 12月, 2006 1 次提交
  2. 08 12月, 2006 3 次提交
    • O
      [PATCH] winbond IDE depends on IDEDMA · 9468f687
      Olaf Hering 提交于
      winbond ide depends on idedma.
      Move the option into the IDEDMA section.
      
        drivers/built-in.o: In function `.sl82c105_ide_dma_timeout':
        sl82c105.c:(.text+0x624d0): undefined reference to `.__ide_dma_timeout'
        drivers/built-in.o: In function `.sl82c105_ide_dma_off_quietly':
        sl82c105.c:(.text+0x6274c): undefined reference to `.__ide_dma_off_quietly'
        drivers/built-in.o: In function `.sl82c105_ide_dma_on':
        sl82c105.c:(.text+0x6284c): undefined reference to `.__ide_dma_on'
        drivers/built-in.o: In function `.sl82c105_check_drive':
        sl82c105.c:(.text+0x628ec): undefined reference to `.__ide_dma_bad_drive'
        sl82c105.c:(.text+0x62934): undefined reference to `.__ide_dma_good_drive'
        drivers/built-in.o: In function `.sl82c105_ide_dma_start':
        sl82c105.c:(.text+0x62c24): undefined reference to `.ide_dma_start'
        make[1]: *** [.tmp_vmlinux1] Error 1
      Signed-off-by: NOlaf Hering <olaf@aepfle.de>
      Acked-by: N"Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9468f687
    • P
      [PATCH] lockdep: fix ide/proc interaction · 9a2239b1
      Peter Zijlstra 提交于
        rmmod/3080 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
         (proc_subdir_lock){--..}, at: [<c04a33b0>] remove_proc_entry+0x40/0x191
      
        and this task is already holding:
         (ide_lock){++..}, at: [<c05651a2>] ide_unregister_subdriver+0x39/0xc8
        which would create a new lock dependency:
         (ide_lock){++..} -> (proc_subdir_lock){--..}
      
        but this new dependency connects a hard-irq-safe lock:
         (ide_lock){++..}
        ... which became hard-irq-safe at:
          [<c043c458>] lock_acquire+0x4b/0x6b
          [<c06129d7>] _spin_lock_irqsave+0x22/0x32
          [<c0567870>] ide_intr+0x17/0x1a9
          [<c044eb31>] handle_IRQ_event+0x20/0x4d
          [<c044ebf2>] __do_IRQ+0x94/0xef
          [<c0406771>] do_IRQ+0x9e/0xbd
      
        to a hard-irq-unsafe lock:
         (proc_subdir_lock){--..}
        ... which became hard-irq-unsafe at:
        ...  [<c043c458>] lock_acquire+0x4b/0x6b
          [<c06126ab>] _spin_lock+0x19/0x28
          [<c04a32f2>] xlate_proc_name+0x1b/0x99
          [<c04a3547>] proc_create+0x46/0xdf
          [<c04a3642>] create_proc_entry+0x62/0xa5
          [<c07c1972>] proc_misc_init+0x1c/0x1d2
          [<c07c1844>] proc_root_init+0x4c/0xe9
          [<c07ad703>] start_kernel+0x294/0x3b3
      
      Move ide_remove_proc_entries() out from under ide_lock; there is nothing
      that indicates that this is needed.
      
      In specific, the call to ide_add_proc_entries() is unprotected, and there
      is nothing else in the file using the respective ->proc fields. Also the
      lock order around destroy_proc_ide_interface() suggests this.
      
      Alan sayeth:
      
        proc_ide_write_settings walks the setting list under ide_setting_sem, read
        ditto.  remove_proc_entry is doing proc side housekeeping.
      
        Looks fine to me, although that old code is such a mess anything could be
        going on.
      Signed-off-by: NPeter Zijlstra <a.p.zijlstra@chello.nl>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9a2239b1
    • A
      [PATCH] via82cxxx: handle error condition properly · 23a1b2a7
      Alan Cox 提交于
      Jeff noted that the via driver returned an error to an unsigned int in a
      a case where errors are not permitted. Move the check down earlier so we
      can handle it properly. Not as pretty but it works this way and avoids
      hacking up ugly stuff in the legacy ide core.
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Cc: Jeff Garzik <jeff@garzik.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      23a1b2a7
  3. 05 12月, 2006 4 次提交
  4. 30 11月, 2006 1 次提交
  5. 26 11月, 2006 1 次提交
  6. 15 11月, 2006 1 次提交
  7. 14 11月, 2006 1 次提交
  8. 13 11月, 2006 1 次提交
  9. 04 11月, 2006 1 次提交
  10. 31 10月, 2006 1 次提交
  11. 29 10月, 2006 1 次提交
  12. 22 10月, 2006 1 次提交
  13. 17 10月, 2006 1 次提交
  14. 16 10月, 2006 1 次提交
  15. 12 10月, 2006 3 次提交
  16. 06 10月, 2006 1 次提交
  17. 05 10月, 2006 1 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells 提交于
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  18. 04 10月, 2006 3 次提交
  19. 03 10月, 2006 13 次提交