summaryrefslogtreecommitdiffstats
path: root/drivers/crypto
diff options
context:
space:
mode:
authorOded Gabbay <ogabbay@kernel.org>2021-09-30 10:36:07 +0200
committerOded Gabbay <ogabbay@kernel.org>2021-10-18 11:05:46 +0200
commita00f1f571e50eb33c5b89db8ac7cd2d684da2943 (patch)
treeb5718d85181ba8502e5391d900405c6cd5ff97df /drivers/crypto
parenthabanalabs: fix debugfs device memory MMU VA translation (diff)
downloadlinux-a00f1f571e50eb33c5b89db8ac7cd2d684da2943.tar.xz
linux-a00f1f571e50eb33c5b89db8ac7cd2d684da2943.zip
habanalabs: define soft-reset as inference op
Soft-reset is the procedure where we reset only the compute/DMA engines of the device, without requiring the current user-space process to release the device. This type of reset can happen if TDR event occurred (a workload got stuck) or by a root request through sysfs. This is only relevant for inference ASICs, as there is no real-world use-case to do that in training, because training runs on multiple devices. In addition, we also do (in certain ASICs) a reset upon device release. That reset uses the same code as the soft-reset. Therefore, to better differentiate between the two resets, it is better to rename the soft-reset support as "inference soft-reset", to make the code more self-explanatory. Signed-off-by: Oded Gabbay <ogabbay@kernel.org>
Diffstat (limited to 'drivers/crypto')
0 files changed, 0 insertions, 0 deletions