Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • cricket cricket
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

Aufgrund eines Sicherheitsupdates wird GitLab am 02.02. zwischen 8:00 und 9:00 Uhr kurzzeitig nicht zur Verfügung stehen. / Due to a security update, GitLab will be temporarily unavailable on 02.02. between 8:00 and 9:00 am.

  • ACS
  • Public
  • Virtualization
  • cricketcricket
  • Merge requests
  • !5

WIP: Feature/cricketd: Isolate host application using RPC

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Niklas Eiling requested to merge feature/cricketd into master May 28, 2019
  • Overview 0
  • Commits 11
  • Pipelines 0
  • Changes 38

We use TI-RPC / rpcgen to create RPC routines that execute driver API calls in a daemon process (cricketd) rather than the host application itself. This way the driver has no chance to map garbage into the host application. The statically linked runtime API can be used without any modifications and calls driver API functions that are intercepted using LD_PRELOAD / libcudawrap.so

I only hope the runtime API can be checkpointed without modifications.

  • First RPC tests
  • Reverse engineer hidden functions (evil cuGetExportTable)
  • Initialize driver using RPC calls
  • Figure out how to start a kernel located in a different binary
  • Implement remaining RPC calls
  • Test checkpointing of isolated host app
  • Integrate with cricket proper
  • clean up
  • Enable remote execution (Have cricketd run on a different node than the host application)
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/cricketd