From 8954f28a7e68c0833230b037ce5b3abbfd5d19bd Mon Sep 17 00:00:00 2001 From: Hrishabh Rajput Date: Wed, 9 Oct 2024 15:01:22 +0530 Subject: [PATCH] ARM: dts: msm: Set vCPU affinity to CPU0 for VMs on Tuna Even though we use proxy scheduling, during VM bootup hypervisor tries to boot the VMs as per the affinity-map. This may cause panic in case a CPU within affinity-map is unavailable. Affining vCPUs to CPU0 makes sure VM proceeds with powered-ON sequence, assuming CPU0 is always available. Change-Id: Ia6799445891e1b003b5055178adb50778bade863 Signed-off-by: Hrishabh Rajput --- qcom/tuna-oemvm.dtsi | 2 +- qcom/tuna-vm.dtsi | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/qcom/tuna-oemvm.dtsi b/qcom/tuna-oemvm.dtsi index 3bbe6c32..74363a94 100644 --- a/qcom/tuna-oemvm.dtsi +++ b/qcom/tuna-oemvm.dtsi @@ -87,7 +87,7 @@ vcpus { config = "/cpus"; affinity = "proxy"; - affinity-map = <0x5 0x6>; + affinity-map = <0x0 0x0>; sched-priority = <0>; /* relative to PVM */ sched-timeslice = <2000>; /* in ms */ }; diff --git a/qcom/tuna-vm.dtsi b/qcom/tuna-vm.dtsi index 830368e7..ae8c40a9 100644 --- a/qcom/tuna-vm.dtsi +++ b/qcom/tuna-vm.dtsi @@ -96,7 +96,7 @@ vcpus { config = "/cpus"; affinity = "proxy"; - affinity-map = <0x5 0x6>; + affinity-map = <0x0 0x0>; sched-priority = <0>; /* relative to PVM */ sched-timeslice = <2000>; /* in ms */ };