Skip to content

C
clone-Linux

gsplhtlxg / clone-Linux

通知 2
Star 0
Fork 1
C
clone-Linux

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 26 10月, 2006 2 次提交
  3. 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
  5. 01 10月, 2006 1 次提交
  7. 24 9月, 2006 2 次提交
  9. 20 8月, 2006 1 次提交
  11. 10 7月, 2006 1 次提交
  13. 10 6月, 2006 2 次提交
  15. 28 2月, 2006 1 次提交
    • C
      [SCSI] aic7xxx: semaphore to completion conversion · 8cac8145
      由 Christoph Hellwig 提交于 
      On Tue, Jan 31, 2006 at 06:20:18PM +0100, Christoph Hellwig wrote:
> switch eh_sem to a completion.  due to wait_for_completion_timeout this
> also nicely simplifies the code.  Unfortunately it's untested, so if
> someone with the hardware could give it a try that would be nice.  Once
> it works the same thing can be applied to aic79xx.

New version that switches to the common onstack completion and just a
pointer in the platform_data struct idiom.  This gets rid of all the
flags fiddling.
Signed-off-by: NChristoph Hellwig <hch@lst.de>
Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      8cac8145
  17. 13 1月, 2006 1 次提交
  19. 15 12月, 2005 1 次提交
  21. 29 11月, 2005 1 次提交
    • V
      [SCSI] aic7xxx: reset handler selects a wrong command · dce20067
      由 Vasily Averin 提交于 
      To transport scsi reset command to device aic7xxx reset handler looks
at the driver's pending_list and searches any proper command. However
the search condition has been inverted: ahc_match_scb() returns TRUE
if a matched command is found. As a result the reset on required
devices did not turn out well, a correctly working neighbour device
may be surprised by the reset. aic7xxx reset handler reports about the
success, but really the original situation is not corrected yet.
Signed-off-by: NVasily Averin <vvs@sw.ru>

Naturally, there's a corresponding problem in the aic79xx driver, so
I've also added the same fix for that.
Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      dce20067
  23. 07 11月, 2005 1 次提交
  25. 29 10月, 2005 2 次提交
  27. 03 10月, 2005 1 次提交
  29. 14 9月, 2005 1 次提交
  31. 05 9月, 2005 1 次提交
  33. 10 8月, 2005 1 次提交
  35. 06 8月, 2005 1 次提交
  37. 05 8月, 2005 2 次提交
  39. 02 8月, 2005 1 次提交
  41. 30 7月, 2005 1 次提交
  43. 12 7月, 2005 2 次提交
  45. 03 7月, 2005 1 次提交
  47. 18 6月, 2005 2 次提交
  49. 14 6月, 2005 1 次提交
  51. 12 6月, 2005 2 次提交
  53. 04 6月, 2005 1 次提交
  55. 27 5月, 2005 1 次提交
  57. 25 5月, 2005 1 次提交
  59. 21 5月, 2005 3 次提交
    • J
      [SCSI] aic7xxx: fix U160 mode · 2bf2c568
      由 James Bottomley 提交于 
      The new period/dt setting routines don't get the coupling of these
parameters correct.  This means that Domain Validation never gets DT
set, and thus the drive gets restricted to U80.

Fix this by restoring the couplings in the set routines.
Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      2bf2c568
    • J
      [SCSI] aic7xxx: add back locking · fb3089df
      由 James Bottomley 提交于 
      Tampering with the settings has to be done under the host lock ...
slave_alloc isn't called under any lock, so this has to be done
explicitly.
Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      fb3089df
    • J
      [SCSI] aic7xxx: make correct use of slave_alloc/destroy and remove the per device timer · c7525233
      由 James Bottomley 提交于 
      The allocation of all of our components should be done in slave alloc.
Currently it's rather fancifully refcounted in the queuecommand
callback.  This patch moves allocation and destroy to their correct
places in slave_alloc/slave_destory.  Now we can guarantee that
everywhere a device is requested, it's actually been allocated, so don't
check for this anymore.

Additionally, the per device busy timer was the only source of potential
use after free.  It's been deleted because Linux does the correct thing
with busy returns, so there's no need to implement a separate timer in
the driver.

Finally, implement code that forces all the device parameters to zero
(i.e. async and narrow) in the slave alloc, inform the spi class of the
bios recorded maximums and wait until slave configure before trying
anything more adventurous.
Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      c7525233