aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-sql.py
diff options
context:
space:
mode:
authorMyron Stowe <[email protected]>2018-08-13 12:19:39 -0600
committerBjorn Helgaas <[email protected]>2018-08-14 09:07:31 -0500
commit3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 (patch)
treebf2dd1c51f096328b6485161eabbc428afc3f011 /tools/perf/scripts/python/call-graph-from-sql.py
parent2d1ce5ec2117d16047334a1aa4b62e0cfb5a0605 (diff)
PCI: Skip MPS logic for Virtual Functions (VFs)
PCIe r4.0, sec 9.3.5.4, "Device Control Register", shows both Max_Payload_Size (MPS) and Max_Read_request_Size (MRRS) to be 'RsvdP' for VFs. Just prior to the table it states: "PF and VF functionality is defined in Section 7.5.3.4 except where noted in Table 9-16. For VF fields marked 'RsvdP', the PF setting applies to the VF." All of which implies that with respect to Max_Payload_Size Supported (MPSS), MPS, and MRRS values, we should not be paying any attention to the VF's fields, but rather only to the PF's. Only looking at the PF's fields also logically makes sense as it's the sole physical interface to the PCIe bus. Link: https://bugzilla.kernel.org/show_bug.cgi?id=200527 Fixes: 27d868b5e6cf ("PCI: Set MPS to match upstream bridge") Signed-off-by: Myron Stowe <[email protected]> Signed-off-by: Bjorn Helgaas <[email protected]> Cc: [email protected] # 4.3+ Cc: Keith Busch <[email protected]> Cc: Sinan Kaya <[email protected]> Cc: Dongdong Liu <[email protected]> Cc: Jon Mason <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions