summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorDamien Le Moal <dlemoal@kernel.org>2025-01-04 07:59:46 +0300
committerKeith Busch <kbusch@kernel.org>2025-01-11 06:30:48 +0300
commit2f2b20fad973d00169d24f5338eb1bf0a42e8218 (patch)
tree0110c57ba0a088fc2510ad83dfb0e6069abf9a0b /tools/perf/scripts/python/exported-sql-viewer.py
parent08461535a9cd9757dadbae0ee3f3bbdd6e66ba09 (diff)
downloadlinux-2f2b20fad973d00169d24f5338eb1bf0a42e8218.tar.xz
nvmet: Implement host identifier set feature support
The NVMe specifications mandate support for the host identifier set_features for controllers that also supports reservations. Satisfy this requirement by implementing handling of the NVME_FEAT_HOST_ID feature for the nvme_set_features command. This implementation is for now effective only for PCI target controllers. For other controller types, the set features command is failed with a NVME_SC_CMD_SEQ_ERROR status as before. As noted in the code, 128 bits host identifiers are supported since the NVMe base specifications version 2.1 indicate in section 5.1.25.1.28.1 that "The controller may support a 64-bit Host Identifier...". The RHII (Reservations and Host Identifier Interaction) bit of the controller attribute (ctratt) field of the identify controller data is also set to indicate that a host ID of "0" is supported but that the host ID must be a non-zero value to use reservations. Signed-off-by: Damien Le Moal <dlemoal@kernel.org> Reviewed-by: Christoph Hellwig <hch@lst.de> Tested-by: Rick Wertenbroek <rick.wertenbroek@gmail.com> Tested-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions