1. 12 2月, 2008 4 次提交
  2. 28 1月, 2008 1 次提交
  3. 20 10月, 2007 1 次提交
  4. 11 10月, 2007 3 次提交
  5. 25 8月, 2007 1 次提交
  6. 12 7月, 2007 1 次提交
  7. 08 5月, 2007 2 次提交
  8. 26 4月, 2007 1 次提交
  9. 09 10月, 2006 1 次提交
  10. 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
  11. 11 9月, 2006 1 次提交
    • D
      [PATCH] Fix dm9000 release_resource · 51985487
      Dirk Opfer 提交于
      dm9000_release_board calls release_resource with the platform resource
      instead of the requested resource:
      
      db->addr_res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
      db->addr_req = request_mem_region(db->addr_res->start, i, pdev->name);
      
      dm9000_release_board:
      
      if (db->addr_res != NULL) {
      release_resource(db->addr_res);
      kfree(db->addr_req);
      
      With this behavior the kernel will crash on the second removal. The
      attached patch fix this problem.
      Signed-off-by: NDirk Opfer <Dirk@Opfer-Online.de>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      51985487
  12. 20 8月, 2006 1 次提交
  13. 03 7月, 2006 1 次提交
  14. 27 6月, 2006 4 次提交
  15. 10 11月, 2005 1 次提交
  16. 09 11月, 2005 1 次提交
    • O
      [PATCH] changing CONFIG_LOCALVERSION rebuilds too much, for no good reason · 733482e4
      Olaf Hering 提交于
      This patch removes almost all inclusions of linux/version.h.  The 3
      #defines are unused in most of the touched files.
      
      A few drivers use the simple KERNEL_VERSION(a,b,c) macro, which is
      unfortunatly in linux/version.h.
      
      There are also lots of #ifdef for long obsolete kernels, this was not
      touched.  In a few places, the linux/version.h include was move to where
      the LINUX_VERSION_CODE was used.
      
      quilt vi `find * -type f -name "*.[ch]"|xargs grep -El '(UTS_RELEASE|LINUX_VERSION_CODE|KERNEL_VERSION|linux/version.h)'|grep -Ev '(/(boot|coda|drm)/|~$)'`
      
      search pattern:
      /UTS_RELEASE\|LINUX_VERSION_CODE\|KERNEL_VERSION\|linux\/\(utsname\|version\).h
      Signed-off-by: NOlaf Hering <olh@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      733482e4
  17. 30 10月, 2005 1 次提交
  18. 29 10月, 2005 1 次提交
  19. 07 9月, 2005 1 次提交
  20. 19 8月, 2005 2 次提交
    • B
      [PATCH] DM9000 - incorrect ioctl() handling · 2ae2d77c
      Ben Dooks 提交于
      The DM9000 driver is responding to ioctl() calls it should not be. This
      can cause problems with the wireless tools incorrectly indentifying the
      device as wireless capable, and crashing under certain operations.
      
      This patch also moves the version printk() to the init call, so that
      you only get it once for multiple devices, and to show it is loaded
      if there are no defined dm9000s
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      2ae2d77c
    • B
      [PATCH] DM9000 - spinlock fixes · 9ef9ac51
      Ben Dooks 提交于
      Fix DM9000 driver usage of spinlocks, which mainly came to light
      when running a kernel with spinlock debugging. These come down to:
      
      1) Un-initialised spin lock
      
      2) Several cases of using  spin_xxx(lock) and not spin_xxx(&lock)
      
      3) move the locking around the phy reg for read/write to only
         keep the lock when actually reading or writing to the phy.
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      9ef9ac51
  21. 27 6月, 2005 1 次提交
  22. 16 5月, 2005 1 次提交