aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/net/lib/py
diff options
context:
space:
mode:
authorNiklas Cassel <[email protected]>2025-03-17 09:57:04 +0000
committerKeith Busch <[email protected]>2025-03-20 23:53:55 +0000
commit1cf0184c0ac4f1e936bb3b089894bbeb0a9eb2bc (patch)
tree52d227649955d0e1fe4319b92d54dfbad1824890 /tools/testing/selftests/net/lib/py
parentnvmet: Remove duplicate uuid_copy (diff)
downloadkernel-1cf0184c0ac4f1e936bb3b089894bbeb0a9eb2bc.tar.gz
kernel-1cf0184c0ac4f1e936bb3b089894bbeb0a9eb2bc.zip
nvmet: pci-epf: Always configure BAR0 as 64-bit
NVMe PCIe Transport Specification 1.1, section 2.1.10, claims that the BAR0 type is Implementation Specific. However, in NVMe 1.1, the type is required to be 64-bit. Thus, to make our PCI EPF work on as many host systems as possible, always configure the BAR0 type to be 64-bit. In the rare case that the underlying PCI EPC does not support configuring BAR0 as 64-bit, the call to pci_epc_set_bar() will fail, and we will return a failure back to the user. This should not be a problem, as most PCI EPCs support configuring a BAR as 64-bit (and those EPCs with .only_64bit set to true in epc_features only support configuring the BAR as 64-bit). Tested-by: Damien Le Moal <[email protected]> Fixes: 0faa0fe6f90e ("nvmet: New NVMe PCI endpoint function target driver") Signed-off-by: Niklas Cassel <[email protected]> Reviewed-by: Christoph Hellwig <[email protected]> Reviewed-by: Chaitanya Kulkarni <[email protected]> Signed-off-by: Keith Busch <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py')
0 files changed, 0 insertions, 0 deletions