summaryrefslogtreecommitdiff
path: root/drivers/accel/habanalabs/gaudi2/gaudi2.c
diff options
context:
space:
mode:
authorKoby Elbaz <kelbaz@habana.ai>2023-01-11 15:43:21 +0200
committerOded Gabbay <ogabbay@kernel.org>2023-01-26 11:52:13 +0200
commita6685b573c8e0e0ec2149e48038b26d6676274f1 (patch)
treea5f21cde0d1d10624d96a55687ed68ae6de4be3f /drivers/accel/habanalabs/gaudi2/gaudi2.c
parent436479522d5691d278d69d4e9478e4a2fb062c6c (diff)
habanalabs: block soft-reset on an unusable device
A device with status malfunction indicates that it can't be used. In such a case we do not support certain reset types, e.g., all kinds of soft-resets (compute reset, inference soft-reset), and reset upon device release. A hard-reset is the only way that an unusable device can change its status. All other reset procedures can't put the device in a reset procedure, which might ultimately cause the device to change its status, unintentionally, to become operational again. Such a scenario has recently occurred, when a user requested a hard-reset while another heavy user workload was ongoing (reset request is queued). Since the workload couldn't finish within reset's timeout limits, the reset has failed and set a device status malfunction. Eventually, when the user released the FD, an unsuccessful soft-reset occurred, hence followed by an additional hard-reset that changed the ASICs status back to be operational. Signed-off-by: Koby Elbaz <kelbaz@habana.ai> Reviewed-by: Oded Gabbay <ogabbay@kernel.org> Signed-off-by: Oded Gabbay <ogabbay@kernel.org>
Diffstat (limited to 'drivers/accel/habanalabs/gaudi2/gaudi2.c')
0 files changed, 0 insertions, 0 deletions