1. 21 3月, 2009 1 次提交
  2. 08 1月, 2009 1 次提交
    • C
      PCI: pci-stub module to reserve pci device · c70e0d9d
      Chris Wright 提交于
      When doing device assignment with KVM there's currently nothing to
      protect the device from having a driver in the host as well as the guest.
      This trivial module just binds the pci device on the host to a stub
      driver so that a real host driver can't bind to the device.  It has no
      pci id table, it supports only dynamic ids.
      
       # echo "8086 10f5" > /sys/bus/pci/drivers/pci-stub/new_id
       # echo -n 0000:00:19.0 > /sys/bus/pci/drivers/e1000e/unbind
       # echo -n 0000:00:19.0 > /sys/bus/pci/drivers/pci-stub/bind
       # ls -l /sys/bus/pci/devices/0000:00:19.0/driver
       lrwxrwxrwx 1 root root 0 2008-11-25 19:10 /sys/bus/pci/devices/0000:00:19.0/driver -> ../../../bus/pci/drivers/pci-stub
      
      Cc: "Kay, Allen M" <allen.m.kay@intel.com>
      Cc: "Nakajima, Jun" <jun.nakajima@intel.com>
      Signed-off-by: NChris Wright <chrisw@sous-sol.org>
      Acked-by: NGreg Kroah-Hartman <gregkh@suse.de>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      c70e0d9d
  3. 06 11月, 2007 1 次提交
  4. 03 5月, 2007 2 次提交
  5. 11 2月, 2007 1 次提交
    • D
      [SPARC64]: Add PCI MSI support on Niagara. · 35a17eb6
      David S. Miller 提交于
      This is kind of hokey, we could use the hardware provided facilities
      much better.
      
      MSIs are assosciated with MSI Queues.  MSI Queues generate interrupts
      when any MSI assosciated with it is signalled.  This suggests a
      two-tiered IRQ dispatch scheme:
      
      	MSI Queue interrupt --> queue interrupt handler
      		MSI dispatch --> driver interrupt handler
      
      But we just get one-level under Linux currently.  What I'd like to do
      is possibly stick the IRQ actions into a per-MSI-Queue data structure,
      and dispatch them form there, but the generic IRQ layer doesn't
      provide a way to do that right now.
      
      So, the current kludge is to "ACK" the interrupt by processing the
      MSI Queue data structures and ACK'ing them, then we run the actual
      handler like normal.
      
      We are wasting a lot of useful information, for example the MSI data
      and address are provided with ever MSI, as well as a system tick if
      available.  If we could pass this into the IRQ handler it could help
      with certain things, in particular for PCI-Express error messages.
      
      The MSI entries on sparc64 also tell you exactly which bus/device/fn
      sent the MSI, which would be great for error handling when no
      registered IRQ handler can service the interrupt.
      
      We override the disable/enable IRQ chip methods in sun4v_msi, so we
      have to call {mask,unmask}_msi_irq() directly from there.  This is
      another ugly wart.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      35a17eb6
  6. 06 1月, 2007 1 次提交
  7. 02 12月, 2006 1 次提交
  8. 30 11月, 2006 2 次提交
  9. 04 11月, 2006 1 次提交
    • A
      PCI: Let PCI_MULTITHREAD_PROBE depend on BROKEN · bb44c308
      Adrian Bunk 提交于
      PCI_MULTITHREAD_PROBE is an interesting feature, but in its current state
      it seems to be more of a trap for users who accidentally enable it.
      
      This patch lets PCI_MULTITHREAD_PROBE depend on BROKEN for 2.6.19.
      
      The intention is to get this patch reversed in -mm as soon as it's in
      Linus' tree, and reverse it for 2.6.20 or 2.6.21 after the fallout of
      in-kernel problems PCI_MULTITHREAD_PROBE causes got fixed.
      
      (akpm: I get enough bug reports already)
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      bb44c308
  10. 12 10月, 2006 1 次提交
    • A
      [PATCH] HT_IRQ must depend on PCI · fbab41cc
      Adrian Bunk 提交于
      CONFIG_PCI=n, CONFIG_HT_IRQ=y results in the following compile error:
      
      ...
        LD      vmlinux
      arch/i386/mach-generic/built-in.o: In function `apicid_to_node':
      summit.c:(.text+0x53): undefined reference to `apicid_2_node'
      arch/i386/kernel/built-in.o: In function `arch_setup_ht_irq':
      (.text+0xcf79): undefined reference to `write_ht_irq_low'
      arch/i386/kernel/built-in.o: In function `arch_setup_ht_irq':
      (.text+0xcf85): undefined reference to `write_ht_irq_high'
      arch/i386/kernel/built-in.o: In function `k7nops':
      alternative.c:(.data+0x1358): undefined reference to `mask_ht_irq'
      alternative.c:(.data+0x1360): undefined reference to `unmask_ht_irq'
      make[1]: *** [vmlinux] Error 1
      
      Bug report by Jesper Juhl.
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Cc: "Eric W. Biederman" <ebiederm@xmission.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      fbab41cc
  11. 04 10月, 2006 2 次提交
    • E
      [PATCH] htirq: tidy up the htirq code · 95d77884
      Eric W. Biederman 提交于
      This moves the declarations for the architecture helpers into
      include/linux/htirq.h from the generic include/linux/pci.h.  Hopefully this
      will make this distinction clearer.
      
      htirq.h is included where it is needed.
      
      The dependency on the msi code is fixed and removed.
      
      The Makefile is tidied up.
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Tony Luck <tony.luck@intel.com>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Greg KH <greg@kroah.com>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      95d77884
    • E
      [PATCH] Initial generic hypertransport interrupt support · 8b955b0d
      Eric W. Biederman 提交于
      This patch implements two functions ht_create_irq and ht_destroy_irq for
      use by drivers.  Several other functions are implemented as helpers for
      arch specific irq_chip handlers.
      
      The driver for the card I tested this on isn't yet ready to be merged.
      However this code is and hypertransport irqs are in use in a few other
      places in the kernel.  Not that any of this will get merged before 2.6.19
      
      Because the ipath-ht400 is slightly out of spec this code will need to be
      generalized to work there.
      
      I think all of the powerpc uses are for a plain interrupt controller in a
      chipset so support for native hypertransport devices is a little less
      interesting.
      
      However I think this is a half way decent model on how to separate arch
      specific and generic helper code, and I think this is a functional model of
      how to get the architecture dependencies out of the msi code.
      
      [akpm@osdl.org: Kconfig fix]
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Cc: Greg KH <greg@kroah.com>
      Cc: Andi Kleen <ak@muc.de>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      8b955b0d
  12. 26 9月, 2006 1 次提交
    • G
      PCI: enable driver multi-threaded probe · 0f397f86
      Greg Kroah-Hartman 提交于
      This provides a build and run-time option to turn on multhreaded probe
      for all PCI drivers.  It can cause bad problems on multi-processor
      machines that take a while to find their root disks, and play havoc on
      machines that don't use persistant device names for block or network
      devices.
      
      But it can cause speedups on some machines, my tiny laptop's boot goes
      up by 0.4 seconds, and my desktop boots up several seconds faster.
      
      Use at your own risk!!!
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      0f397f86
  13. 24 3月, 2006 2 次提交
  14. 09 9月, 2005 1 次提交
  15. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4