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

Xen extended regions should work correctly with z_mem_phys_addr and Z_MEM_PHYS_ADDR #68

Open
xakep-amatop opened this issue Jul 18, 2023 · 1 comment
Labels
bug Something isn't working Xen

Comments

@xakep-amatop
Copy link
Collaborator

We have to deal with Xen extended regions. The function z_mem_phys_addr and the macro Z_MEM_PHYS_ADDR aren't able to work with Xen extended regions. So, it can be used as for common cases.

I think that we need to add some code inside z_mem_phys_addr and Z_MEM_PHYS_ADDR, specifically changing the checks if we want to work with extended regions.

Note, in Linux, for example, Extended regions are implemented as hot-pluggable memory, so Linux mm subsystem can handle them correctly. So, probably we need to implement smth like this.

@xakep-amatop xakep-amatop added bug Something isn't working Xen labels Jul 18, 2023
@xakep-amatop
Copy link
Collaborator Author

xakep-amatop commented Jan 29, 2024

remove this WA after fixing the issue aosedge/aos_core_zephyr@4b04100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Xen
Projects
None yet
Development

No branches or pull requests

1 participant