[Android] Runtime/BCL native libs need support for devices with 16k memory pages (arm64 and x64)

[grendello]

Wiki: https://github.com/xamarin/xamarin-android/wiki/Android-support-for-devices-with-16k-pages

Summary

Android is moving towards supporting devices with 16k memory page size, for the x64 and arm64 architectures. This affects all the native components of the application. In our case it means the MonoVM runtime, the BCL support libraries and .NET for Android native runtime and libraries.

Google plan to make support for 16k devices a requirement for Google Play application submissions next year.

A lot of work needs to be done.

Google have an article with more technical details.

How it affects the runtime

• All the native libraries must be rebuilt with flags enabling 16k alignment of data and code
• Code review of native (and maybe some managed?) code needs to be done in order to make sure we don't assume 4k page size anywhere. This includes MonoVM runtime/JIT/interpreter code.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

[steveisok]

/cc @vitek-karas

[janvorli]

• Code review of native (and maybe some managed?) code needs to be done in order to make sure we don't assume 4k page size anywhere

coreclr should work on variable page sizes. macOS ARM64 uses 16kB pages, we have tested Linux arm64 with 64kB pages in the past too. I am not sure about the x64 though, there might be some stuff expecting 4kB page size for this architecture.

[janvorli]

Ah, sorry, this issue is mono specific, right?

[steveisok]

Ah, sorry, this issue is mono specific, right?

Yeah, but it's also important to understand how coreclr would behave.

[grendello]

@janvorli CoreCLR is used to build apps that run on Android too, so as @steveisok said, it's important to make sure it works too.