Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • O OSKernel2024-10183_BOOT-2934
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • 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
  • educg-net-28665-2608131
  • OSKernel2024-10183_BOOT-2934
  • Repository
"kernel/exec.c" did not exist on "05d66b06294df89ba3d5b8f6cf535f7edf00bd1f"
  • T202410183994455-2934
  • kernel
  • exec.c
Find file BlameHistoryPermalink
  • Frans Kaashoek's avatar
    Checkpoint switching to per-process locks, in attempt clarify xv6's · 67702cf7
    Frans Kaashoek authored Jul 02, 2019
    locking plan, which is a difficult to understand because ptable lock
    protects many invariants.  This implementation has a bug: once in a
    while xv6 unlocks a proc lock that is locked by another core.
    67702cf7