+26
−26
Loading
Merge Pull Request from: @cj-xiaocai THe fix is a bit involved, and relies on 3 things: - Making sure that the initial affinity of a VPE is fixed at activate time, which is done early in the life of the vcpup, before it can run. - Add a per-VM lock that can be taken instead of the global vmovp_lock, paving the way for a more manageable lock order. - Take the per-VPE lock whenever modifying the VPE affinity, as expected everywhere else in the code. With that, VMAPP and VMOVP can now run concurrently and still lead to sensible results. https://gitee.com/openeuler/kernel/issues/IAVK49 Link:https://gitee.com/openeuler/kernel/pulls/12065 Reviewed-by:Zhang Jianhua <chris.zjh@huawei.com> Signed-off-by:
Zhang Peng <zhangpeng362@huawei.com>