1. 09 8月, 2016 1 次提交
  2. 22 7月, 2016 5 次提交
  3. 20 12月, 2015 1 次提交
  4. 05 12月, 2015 1 次提交
  5. 01 12月, 2015 1 次提交
  6. 16 10月, 2015 4 次提交
  7. 14 10月, 2015 1 次提交
  8. 19 9月, 2015 1 次提交
  9. 21 8月, 2015 1 次提交
  10. 31 7月, 2015 1 次提交
  11. 30 7月, 2015 3 次提交
  12. 23 7月, 2015 6 次提交
  13. 17 7月, 2015 2 次提交
  14. 07 5月, 2015 3 次提交
  15. 28 1月, 2015 1 次提交
    • Y
      PCI: Fail MSI-X mappings if there's no space assigned to MSI-X BAR · 6a878e50
      Yijing Wang 提交于
      Unlike MSI, which is configured via registers in the MSI capability in
      Configuration Space, MSI-X is configured via tables in Memory Space.
      These MSI-X tables are mapped by a device BAR, and if no Memory Space
      has been assigned to the BAR, MSI-X cannot be used.
      
      Fail MSI-X setup if no space has been assigned for the BAR.
      
      Previously, we ioremapped the MSI-X table even if the resource hadn't been
      assigned.  In this case, the resource address is undefined (and is often
      zero), which may lead to warnings or oopses in this path:
      
        pci_enable_msix
          msix_capability_init
            msix_map_region
              ioremap_nocache
      
      The PCI core sets resource flags to zero when it can't assign space for the
      resource (see reset_resource()).  There are also some cases where it sets
      the IORESOURCE_UNSET flag, e.g., pci_reassigndev_resource_alignment(),
      pci_assign_resource(), etc.  So we must check for both cases.
      
      [bhelgaas: changelog]
      Reported-by: NZhang Jukuo <zhangjukuo@huawei.com>
      Tested-by: NZhang Jukuo <zhangjukuo@huawei.com>
      Signed-off-by: NYijing Wang <wangyijing@huawei.com>
      Signed-off-by: NBjorn Helgaas <bhelgaas@google.com>
      6a878e50
  16. 24 11月, 2014 2 次提交
  17. 23 11月, 2014 6 次提交