Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • K kvmtool-dm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linux-arm
  • kvmtool-dm
  • Repository
Switch branch/tag
  • kvmtool-dm
  • kvm.c
Find file BlameHistoryPermalink
  • Jean-Philippe Brucker's avatar
    Prevent segfault when kvm_pause is called too early · 37b8e06b
    Jean-Philippe Brucker authored Nov 03, 2017
    
    
    When kvm_pause is called early (from taking the rwlock), it segfaults
    because the CPU array is initialized slightly later. Fix this.
    
    This doesn't happen at the moment but the gicv2m patch will register an
    MMIO region, which requires br_write_lock. gicv2m is instantiated by
    kvm__arch_init from within core_init (level 0). The CPU array is
    initialized later in base_init (level 1).
    
    Signed-off-by: Jean-Philippe Brucker's avatarJean-Philippe Brucker <jean-philippe.brucker@arm.com>
    Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
    37b8e06b