system: add EFI variable validation testcase#432
Open
smuppand wants to merge 1 commit intoqualcomm-linux:mainfrom
Open
system: add EFI variable validation testcase#432smuppand wants to merge 1 commit intoqualcomm-linux:mainfrom
smuppand wants to merge 1 commit intoqualcomm-linux:mainfrom
Conversation
Add a System testcase to validate EFI kernel config, efivar runtime availability, OsTrialBootStatus write and readback, and OsIndicationsSupported attribute and value checks. This helps catch regressions where EFI support is enabled in kernel config but EFI variable access or expected UEFI variable behavior is not functioning correctly on target. Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a new System testcase for EFI variable validation.
Why this PR is needed:
Having EFI-related kernel config enabled is not enough by itself to prove that EFI runtime functionality is working correctly on target. We also need to validate the actual efivar runtime path and confirm that EFI variables can be enumerated, written, and read back with the expected attributes and values.
What this PR adds:
Why this is useful:
This helps catch regressions where EFI support appears enabled in kernel config but the runtime EFI variable service is not working correctly. It also validates that the expected UEFI variable attributes and payloads are reflected correctly on target, which is important for platform bring-up, firmware integration, and runtime EFI validation.