Enable KVM by default on IQ-615-EVK#2366
Conversation
vkraleti
requested review from
anujm1,
koenkooi,
lumag,
ndechesne and
ricardosalveti
as code owners
Test Results 102 files 631 suites 5h 9m 54s ⏱️ For more details on these failures, see this check. Results for commit 5b38c92. ♻️ This comment has been updated with latest results. |
| require conf/machine/include/qcom-qcs615.inc | ||
|
|
||
| MACHINE_FEATURES += "efi pci" | ||
| MACHINE_FEATURES += "efi kvm pci" |
There was a problem hiding this comment.
qcs615-ride is not yet using multi-dtb, wouldn't that be an issue?
There was a problem hiding this comment.
Without multi-dtb, device is booting but PILs are not up. Similar behavior on qcs8300-ride-sx & qcs9100-ride-sx as well. Should they be reverted back to 'Gunyah'?
There was a problem hiding this comment.
Either we disable kvm or migrate to multi-dtb, but I remember multi-dtb would also cause these boards to stop booting (due our current hw availability, not using the iot variants), so I guess our only option is to use gunyah by default.
There was a problem hiding this comment.
I dropped qcs615-ride changes. I'll revert kvm enablement changes for qcs8300-ride-sx & qcs9100-ride-sx in another PR.
There was a problem hiding this comment.
Or enable non-IoT devices as a temporal measure. Should we patch qcom-dtb-metadata inside the meta-qcom?
There was a problem hiding this comment.
Maybe send a change to qcom-dtb-metadata itself. This is just a database update. Should not be any objections to accept it.
There was a problem hiding this comment.
@vkraleti we have discussed it several times, I think. The kernel team doesn't want to support non-IoT SKUs.
There was a problem hiding this comment.
For now, to avoid functionality breakages on Ride boards, let's switch back to Gunyah. If there is a general agreement for KVM on Ride, can make necessary changes. I'll start internal email regd. this.
Enable KVM by default on iq-615-evk by adding 'kvm' to MACHINE_FEATURES. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
Update FIT_DTB_COMPATIBLE entries for Talos platforms to use talos-el2.dtbo by default, enabling KVM configurations. Replace el2kvm-specific compatible strings with default variants to align with the KVM-by-default behavior. Update non-EL2 entries to use `el2gh` substring in compatible strings, indicating mapping to the Gunyah hypervisor. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
KVM is now enabled by default on iq-615-evk, making the dedicated KVM build is redundent. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>
vkraleti
changed the title
4 participants
All PILs are functioning correctly and KVM can be enabled by default on IQ-615-EVK.
Update FIT_DTB_COMPATIBLE entries and machine configurations to switch to default KVM.