1. 14 Jun, 2013 8 commits
  2. 10 Jun, 2013 1 commit
  3. 07 Jun, 2013 4 commits
  4. 06 Jun, 2013 7 commits
  5. 05 Jun, 2013 4 commits
  6. 04 Jun, 2013 2 commits
  7. 03 Jun, 2013 5 commits
  8. 01 Jun, 2013 2 commits
    • Bjorn Helgaas's avatar
      Merge branch 'pci/misc' into next · 0345d3f8
      Bjorn Helgaas authored
      * pci/misc:
        PCI: Replace strict_strtoul() with kstrtoul()
        PCI: Fix comment typo for PCI_EXP_LNKCAP_CLKPM
        PCI: Replace printks with appropriate pr_*()
        PCI: Fix kerneldoc for pci_disable_link_state()
        x86/PCI: Increase info->res_num before checking pci_use_crs
        PCI: Fix INTC comment typo for pci_swizzle_interrupt_pin()
        PCI: Convert ioapic.c to module_pci_driver
      0345d3f8
    • Jingoo Han's avatar
      PCI: Replace strict_strtoul() with kstrtoul() · 9a994e8e
      Jingoo Han authored
      The usage of strict_strtoul() is not preferred, because
      strict_strtoul() is obsolete.  Thus, kstrtoul() should be
      used.
      
      [bhelgaas: "#define strict_strtoul  kstrtoul", so no functional change]
      Signed-off-by: default avatarJingoo Han <jg1.han@samsung.com>
      Signed-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
      9a994e8e
  9. 31 May, 2013 1 commit
    • Xudong Hao's avatar
      PCI: Finish SR-IOV VF setup before adding the device · fbf33f51
      Xudong Hao authored
      Commit 4f535093 "PCI: Put pci_dev in device tree as early as possible"
      moves device registering from pci_bus_add_devices() to pci_device_add().
      That causes problems for virtual functions because device_add(&virtfn->dev)
      is called before setting the virtfn->is_virtfn flag, which then causes Xen
      to report PCI virtual functions as PCI physical functions.
      
      Fix it by setting virtfn->is_virtfn before calling pci_device_add().
      
      [Jiang Liu]: Move the setting of virtfn->is_virtfn ahead further for better
      readability and modify changelog.
      Signed-off-by: default avatarXudong Hao <xudong.hao@intel.com>
      Signed-off-by: default avatarJiang Liu <jiang.liu@huawei.com>
      Signed-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
      Cc: stable@vger.kernel.org	# v3.9+
      fbf33f51
  10. 29 May, 2013 5 commits
  11. 28 May, 2013 1 commit
    • Alexander Gordeev's avatar
      PCI: Allocate only as many MSI vectors as requested by driver · 65f6ae66
      Alexander Gordeev authored
      Because of the encoding of the "Multiple Message Capable" and "Multiple
      Message Enable" fields, a device can only advertise that it's capable of a
      power-of-two number of vectors, and the OS can only enable a power-of-two
      number.
      
      For example, a device that's limited internally to using 18 vectors would
      have to advertise that it's capable of 32.  The 14 extra vectors consume
      vector numbers and IRQ descriptors even though the device can't actually
      use them.
      
      This fix introduces a 'msi_desc::nvec_used' field to address this issue.
      When non-zero, it is the actual number of MSIs the device will send, as
      requested by the device driver.  This value should be used by architectures
      to set up and tear down only as many interrupt resources as the device will
      actually use.
      
      Note, although the existing 'msi_desc::multiple' field might seem
      redundant, in fact it is not.  The number of MSIs advertised need not be
      the smallest power-of-two larger than the number of MSIs the device will
      send.  Thus, it is not always possible to derive the former from the
      latter, so we need to keep them both to handle this case.
      
      [bhelgaas: changelog, rename to "nvec_used"]
      Signed-off-by: default avatarAlexander Gordeev <agordeev@redhat.com>
      Signed-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
      65f6ae66