1. 01 9月, 2007 1 次提交
  2. 27 6月, 2007 1 次提交
  3. 12 5月, 2007 1 次提交
  4. 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. 03 7月, 2006 1 次提交
  6. 29 6月, 2006 1 次提交
  7. 22 6月, 2006 1 次提交
  8. 24 3月, 2006 1 次提交
  9. 17 1月, 2006 1 次提交
  10. 16 12月, 2005 1 次提交
  11. 10 9月, 2005 1 次提交
  12. 08 9月, 2005 2 次提交
  13. 27 8月, 2005 1 次提交
  14. 12 8月, 2005 2 次提交
  15. 13 7月, 2005 1 次提交
    • C
      [IA64] Altix pcibus_to_node implementation · 7c2a6c62
      Christoph Lameter 提交于
      The Altix subarch does not provide node information via ACPI. Instead hooks
      are used to fixup pci structures. This patch determines the nodes for Altix
      PCI busses.
      
      Remote Bridges:
      ---------------
      Altix supports remote I/O nodes without memory or processors but with bridges.
      The TIOCA type of bridge is an AGP bridge and the PROM provides information
      about the closest node. That information will be returned by pcibus_to_node.
      
      The TIOCP remote bridge type is a PCI bridge but the PROM does not provide a
      closest node id. pcibus_to_node will return -1 for devices on those bridges
      meaning that device control structures may be allocated on any node.
      
      Safeguard:
      ----------
      Should the fixups result in invalid node information for a pci controller then
      a warning will be printed and pcibus_to_node will return -1.
      
      
      This patch also fixes the "FIXME" in sn_dma_alloc_coherent. This means that
      dma_alloc_coherent will now use alloc_pages_node to allocate memory local to
      the node that the PCI device is connected to.
      Signed-off-by: NChristoph Lameter <clameter@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      7c2a6c62
  16. 07 7月, 2005 1 次提交
  17. 29 6月, 2005 1 次提交
  18. 04 5月, 2005 1 次提交
  19. 26 4月, 2005 2 次提交