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

TK1 and ODROID_XU4 fail CACHEFLUSH0001 #80

Open
lsf37 opened this issue Oct 6, 2022 · 3 comments
Open

TK1 and ODROID_XU4 fail CACHEFLUSH0001 #80

lsf37 opened this issue Oct 6, 2022 · 3 comments

Comments

@lsf37
Copy link
Member

lsf37 commented Oct 6, 2022

In config ODROID_XU4_debug_hyp_MCS_clang_32 (and apparently only this config and only on clang), ODROID_XU4 is failing the test CACHEFLUSH0001. The configuration is disabled for tests for now.

It looks like this might be a problem with the test setup, not with MCS.

See also discussion on seL4/seL4#877.

@lsf37 lsf37 changed the title ODROID_XU4 fails CACHEFLUSH0001 TK1 and ODROID_XU4 fail CACHEFLUSH0001 Nov 10, 2022
@lsf37
Copy link
Member Author

lsf37 commented Nov 10, 2022

Occasionally the TK1 board also fails the same test (for the same config, i.e. TK1_debug_hyp_MCS_clang_32).

It looks like something is definitely up there.

@lsf37
Copy link
Member Author

lsf37 commented Nov 10, 2022

Comment from Indan on that thread linked above about what might be wrong:

Running test CACHEFLUSH0001 (Test a cache maintenance on pages)
*ptrc == 0xBEEFCAFE at line 104 of file /github/workspace/projects/sel4test/apps/sel4test-tests/src/tests/cache.c

I'm not convinced that test_page_flush is correct: It relies on no cache miss or prefetching happening between the seL4_ARM_Page_Invalidate_Data call and the *ptr write. I don't think that's guaranteed.

In case the invalidation performs an implicit clean, the result is the same as for seL4_ARM_Page_CleanInvalidate_Data above, which is already tested.

@Indanz
Copy link
Contributor

Indanz commented Jun 25, 2023

This seems a duplicate/extension of #65 btw.

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

No branches or pull requests

2 participants