On 05/02/2024 10:14, Tian, Kevin wrote:
From: Yishai Hadas <yishaih@xxxxxxxxxx>
Sent: Wednesday, January 31, 2024 1:02 AM
Let firmware knows upon leaving PRE_COPY back to RUNNING as of some
error in the target/migration cancellation.
This will let firmware cleaning its internal resources that were turned
on upon PRE_COPY.
The flow is based on the device specification in this area.
Signed-off-by: Yishai Hadas <yishaih@xxxxxxxxxx>
if fw internal resource is not cleaned will it lead to an immediate error
upon next migration attempt or a failure after many attempts until
internal resources are used up?
if the former it might worth a 'Fixed' tag.
No, the following migration attempts will succeed.
It just let the firmware to *not* waste some resources to track changes
upon PRE_COPY, as the state was moved back to RUNNING.
Yishai
