ci: append efi=runtime to kernel cmdline for RT builds#2333
ci: append efi=runtime to kernel cmdline for RT builds#2333apateriy-qcom wants to merge 1 commit into
Conversation
Test Results 101 files + 42 622 suites +341 6h 27m 31s ⏱️ + 3h 35m 48s For more details on these failures, see this check. Results for commit 4b91374. ± Comparison against base commit 79d0169. This pull request removes 2 and adds 26 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
lumag
left a comment
There was a problem hiding this comment.
From: Anurag Pateriya anurag.pateriya@oss.qualcomm.com
Signed-off-by: Anurag Pateriya apateriy@qti.qualcomm.com
Which breaks DCO check.
Also, you are just stating that EFI Runtime services require a bootparam on RT kernels. Please point out why does it affect only RT kernels.
2ee249f to
4703df8
Compare
RT kas configs were missing the efi=runtime boot parameter that are preesnt in non-RT builds. Without it, EFI runtime services (efivars) are not accessible, preventing KVM boot (enabling virtualization with el2kvm) on kodiak-el2 and breaking watchdog/dump collection and remoteproc/PIL cores on RT builds. Append efi=runtime to KERNEL_CMDLINE_EXTRA in both RT kas configs (linux-qcom-next-rt.yml and linux-qcom-rt-6.18.yml). Signed-off-by: Anurag Pateriya <apateriy@qti.qualcomm.com>
lumag
left a comment
There was a problem hiding this comment.
RT kas configs were missing the efi=runtime boot parameter that are
preesnt in non-RT builds
I don't see efi=runtime being set in any of the non-RT builds. Pleae point out, where they are set.
Without efi=runtime, EFI runtime services are not available in the RT kernel, which prevents efivars updates (e.g. VendorDtbOverlays), breaks watchdog/dump collection, and causes remoteproc/PIL cores to show as offline on RT-KVM builds.
Append efi=runtime to KERNEL_CMDLINE_EXTRA in both RT kas configs (linux-qcom-next-rt.yml and linux-qcom-rt-6.18.yml) . EFI runtime services are already enabled for non-RT builds.