Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • R rmm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • redox-osredox-os
  • rmm
  • Merge requests
  • !7

aarch64: fix Arch::virt_is_valid

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Pavel Skripkin requested to merge paskripkin/rmm:t1sz into master Nov 19, 2022
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 1

Currently Arch::virt_is_valid is empty stub that returns true for every virtual address for aarch64. armv8 has a notion of valid virtual addresses, which is controlled by TCR_EL1::T1SZ and TCR_EL1::T0SZ for kernel space and user space respectively.

Use TCR_EL1::T1SZ register to determine if virtual address is valid or not

PS: seems like T1SZ is actually hard-coded and always has value of 48. Should we rely on that or better to create a function which will always work?

Signed-off-by: Pavel Skripkin paskripkin@gmail.com

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: t1sz