Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • Q qemu
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • Xing Lin
  • qemu
  • Repository
  • qemu
  • block-migration.c
Find file Blame History Permalink
  • Liran Schour's avatar
    Try not to exceed max downtime on stage3 · 889ae39c
    Liran Schour authored Jan 26, 2010
    
    
    Move to stage3 only when remaining work can be done below max downtime.
    Use qemu_get_clock_ns for measuring read performance.
    
    Signed-off-by: default avatarLiran Schour <lirans@il.ibm.com>
    Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
    889ae39c