Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • linux-vf linux-vf
  • 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 & Registries
    • Packages & 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
  • linux-vflinux-vf
  • Repository
Switch branch/tag
  • linux-vf
  • tools
  • testing
  • selftests
  • vDSO
  • vdso_config.h
Find file BlameHistoryPermalink
  • Vincenzo Frascino's avatar
    kselftest: Extend vdso correctness test to clock_gettime64 · b26c0924
    Vincenzo Frascino authored May 06, 2020
    
    
    With the release of Linux 5.1 has been added a new syscall,
    clock_gettime64, that provided a 64 bit time value for a specified
    clock_ID to make the kernel Y2038 safe on 32 bit architectures.
    
    Extend the vdso correctness test to cover the newly exposed vdso
    function.
    
    Cc: Shuah Khan <shuah@kernel.org>
    Signed-off-by: Vincenzo Frascino's avatarVincenzo Frascino <vincenzo.frascino@arm.com>
    b26c0924