1. 15 5月, 2018 3 次提交
  2. 12 5月, 2018 4 次提交
  3. 11 5月, 2018 3 次提交
  4. 04 5月, 2018 1 次提交
  5. 03 5月, 2018 1 次提交
  6. 30 4月, 2018 1 次提交
  7. 18 4月, 2018 1 次提交
  8. 01 4月, 2018 2 次提交
  9. 30 3月, 2018 1 次提交
  10. 27 3月, 2018 1 次提交
  11. 26 3月, 2018 4 次提交
  12. 22 3月, 2018 5 次提交
  13. 18 3月, 2018 1 次提交
  14. 17 3月, 2018 1 次提交
  15. 13 3月, 2018 1 次提交
  16. 12 3月, 2018 2 次提交
  17. 10 3月, 2018 1 次提交
  18. 08 3月, 2018 3 次提交
  19. 05 3月, 2018 1 次提交
  20. 02 3月, 2018 2 次提交
  21. 17 2月, 2018 1 次提交
    • C
      PCI/cxgb4: Extend T3 PCI quirk to T4+ devices · 7dcf688d
      Casey Leedom 提交于
      We've run into a problem where our device is attached
      to a Virtual Machine and the use of the new pci_set_vpd_size()
      API doesn't help.  The VM kernel has been informed that
      the accesses are okay, but all of the actual VPD Capability
      Accesses are trapped down into the KVM Hypervisor where it
      goes ahead and imposes the silent denials.
      
      The right idea is to follow the kernel.org
      commit 1c7de2b4 ("PCI: Enable access to non-standard VPD for
      Chelsio devices (cxgb3)") which Alexey Kardashevskiy authored
      to establish a PCI Quirk for our T3-based adapters. This commit
      extends that PCI Quirk to cover Chelsio T4 devices and later.
      
      The advantage of this approach is that the VPD Size gets set early
      in the Base OS/Hypervisor Boot and doesn't require that the cxgb4
      driver even be available in the Base OS/Hypervisor.  Thus PF4 can
      be exported to a Virtual Machine and everything should work.
      
      Fixes: 67e65879 ("cxgb4: Set VPD size so we can read both VPD structures")
      Cc: <stable@vger.kernel.org>  # v4.9+
      Signed-off-by: NCasey Leedom <leedom@chelsio.com>
      Signed-off-by: NArjun Vynipadath <arjun@chelsio.com>
      Signed-off-by: NGanesh Goudar <ganeshgr@chelsio.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      7dcf688d