Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add validity checks in rtt_map_unprotected #220

Merged
merged 2 commits into from
Oct 30, 2023

Conversation

zpzigi754
Copy link
Collaborator

This PR adds missing checks in rtt_map_unprotected. All the tests in ACS's rtt_map_unprotected will be passed after this change.

[before]

TOTAL TESTS     : 51

TOTAL PASSED    : 29

TOTAL FAILED    : 19

[after]

TOTAL TESTS     : 51

TOTAL PASSED    : 30

TOTAL FAILED    : 18

@zpzigi754 zpzigi754 changed the title Pass the checks in rtt_map_unprotected Add validity checks in rtt_map_unprotected Oct 27, 2023
scripts/fvp-cca Outdated
@@ -570,6 +570,9 @@ if __name__ == "__main__":
prepare_nw_aosp(args.no_prebuilt_initrd)
prepare_bootloaders(args.rmm, PREBUILT_EDK2, args.hes)
elif args.normal_world == "acs":
# Clear out build directory so that the current target is
# not confused by the previous target
run(["rm", "-rf", "build"], cwd=ACS)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[IMHO] I think it's enough to clean only when with --clean option or remove manually than removing every time.

Copy link
Collaborator Author

@zpzigi754 zpzigi754 Oct 30, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good opinion! I also think that it might be enough to explicitly clean with ./scripts/fvp-cca --clean or manually deleting third-party/cca-rmm-acs/build.

Currently, ./scripts/fvp-cca --clean not only clean ACS, but also clean other third-party submodules (tf-a, kvmtool realm-linux, etc) altogether which I wanted to avoid (e.g., building realm-linux after clearing would take a lot of time). For the second option, it requires an internal knowledge about the ACS's build system which users might not be aware of.

In my personal experience, building acs from the initial state (after removing build dir) did not add much time (a few seconds) in the testing because the module size is relatively small. That's the reason why I chose building ACS from the initial state every time.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will make scripts/fvp-cca --clean into scripts/fvp-cca --clean <target> (e.g., scripts/fvp-cca --clean acs) and do not remove build directory every time after leaving some comment that acs should be cleaned if selected-tests or excluded-tests are used!

This will pass the whole tests in ACS's rtt_map_unprotected.
[before]
./scripts/fvp-cca --clean

[after]
./scripts/fvp-cca --clean <target>
e.g., ./scripts/fvp-cca --clean all
      ./scripts/fvp-cca --clean acs
@zpzigi754 zpzigi754 merged commit b4eb98e into islet-project:main Oct 30, 2023
7 checks passed
@zpzigi754 zpzigi754 deleted the fix-rtt-map-unprotected branch October 30, 2023 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants