summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorNiklas Cassel <cassel@kernel.org>2025-03-17 12:57:04 +0300
committerKeith Busch <kbusch@kernel.org>2025-03-21 02:53:55 +0300
commit1cf0184c0ac4f1e936bb3b089894bbeb0a9eb2bc (patch)
tree52d227649955d0e1fe4319b92d54dfbad1824890 /tools/perf/scripts/python/stackcollapse.py
parent7b658153f1b8a79ed98980f2fef7b92a66aeb9cd (diff)
downloadlinux-1cf0184c0ac4f1e936bb3b089894bbeb0a9eb2bc.tar.xz
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 <dlemoal@kernel.org> Fixes: 0faa0fe6f90e ("nvmet: New NVMe PCI endpoint function target driver") Signed-off-by: Niklas Cassel <cassel@kernel.org> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com> Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions