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.

Sign up for GitHub

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

Jump to bottom

[arch][arm64] Fix mmu_unmap issue when FEAT_TTL is implemented #386

Merged
merged 1 commit into from
Sep 25, 2023
Merged

[arch][arm64] Fix mmu_unmap issue when FEAT_TTL is implemented #386

merged 1 commit into from
Sep 25, 2023

Commits on Aug 30, 2023

  1. [arch][arm64] Fix mmu_unmap issue when FEAT_TTL is implemented 

    Precisely set bits [55:22] of the vaddress in bits [43:0] for the vae1is
and vaee1is TLBI commands.

On platforms where FEAT_TLL is implemented, bits [47:44] of the command
accept a TTL parameter which can optionally be set to hint the
translation table level containing the address being invalidated.
Implementations aren't architecturally required to perform the
invalidation if the hint is incorrect however. Invalidations may
therefore fail with the current implementation if the vaddress has bits
set in [58:55].

This is notably an issue on ARM fastmodels which doesn't perform the
invalidation when the TTL parameter is incorrect.
    @shavitmichael
    shavitmichael committed Aug 30, 2023
    Configuration menu
    Copy the full SHA
    64e2f8a View commit details
    Browse the repository at this point in the history