SlideShare ist ein Scribd-Unternehmen logo
1 von 46
Downloaden Sie, um offline zu lesen
Implement Checkpointing for
         Android
(to speed up boot time and development process)




Jim Huang ( 黃敬群 ) <jserv@0xlab.org>
Kito Cheng ( 程皇嘉 ) <kito@0xlab.org>
Developer, 0xlab
                   Nov 5, 2012 ! Embedded Linux Conference Europe
Rights to copy
                                                                   © Copyright 2012 0xlab
                                                                          http://0xlab.org/
                                                                           contact@0xlab.org
Attribution – ShareAlike 3.0
                                               Corrections, suggestions, contributions and translations
You are free                                                                             are welcome!
   to copy, distribute, display, and perform the work
   to make derivative works                                               Latest update: Nov 21, 2012
   to make commercial use of the work
Under the following conditions
      Attribution. You must give the original author credit.
      Share Alike. If you alter, transform, or build upon this work, you may distribute the
      resulting work only under a license identical to this one.
   For any reuse or distribution, you must make clear to others the license terms of this work.
   Any of these conditions can be waived if you get permission from the copyright holder.
Your fair use and other rights are in no way affected by the above.
License text: http://creativecommons.org/licenses/by-sa/3.0/legalcode
Basic Idea: Process Migration

• Process Migration (in past applications)
   – Distributed Load Balancing
   – Efficient Resource Utilization
• Crash Recovery and Rollback Transaction
  – Useful to system admin

    Processes     Checkpoint   Processes   Processes
     Library                    Library     Library

     TCP/IP                     TCP/IP      TCP/IP
     Node                       Node         Node

                Communication Channel
Checkpointing
• From Wikipedia:
   – … is a technique for inserting fault tolerance into
     computing systems. It basically consists of storing a
     snapshot of the current application state, and later
     on, use it for restarting the execution in case of
     failure.
• Used in distributed shared memory systems
• Even used in reversible debugger
• Different from virtual machine level snapshot/resume
  mechanisms
   – Checkpointing emphasizes on process level.
Ideas about Checkpointing for Android

• Resume to stored state for faster Android boot time
• Better product field trial experience due to regular
  checkpointing
• Deploy problematic states for engineering analysis and
  debugging transparently
• Q&A stress test purpose
Expectations of Checkpointing

• Application-transparent
  – supports applications without modifications or recompilation

• Supports a broad class of applications
  – Databases
  – parallel / MPI apps
  – desktop apps

• Comprehensive support for user-level state,
  kernel-level state, and distributed computation and
  communication state
• Supported on unmodified Linux kernel
  – checkpoint-restart should be integrated by addons
Challenges in checkpoint and restore

  • Network stack will continue to execute even after
    application processes are stopped
  • No system call interface to read or write control state
  • No system call interface to read send socket buffers
  • No system call interface to write receive socket buffers
  • Consistency of control state and socket buffer state
Communication state checkpoint
• Acquire network stack locks to
  freeze TCP processing                             Control                             Control
                                                                     direct
• Save receive buffers using                        Timers,
                                                    Options,         access
                                                                                        Timers,
                                                                                        Options,
  socket receive system call in                     etc.                                etc.

  peek mode
                                    copied_seq    Rh     St+1        write_seq Rt+1 Rh  X     X
                                                                                             St+1        Sh
• Save send buffers by walking           rcv_nxt Rt+1     Sh         snd_una        Rt+1      Sh

  kernel structures                                                   direct
                                               Rh               St    access       Rh               St
• Copy control state from kernel
  structures                                    .
                                                .               .
                                                                .
                                                                receive()
                                                .               .                                  Sh
                                                                                   Rt
• Modify two sequence numbers                                                    Recv          Send
  in saved state to reflect empty              Rt              Sh                buffers       buffers
                                        Recv buffers      Send buffers
  socket buffers
                                    Live Communication State                   Checkpoint State
                                           State for one socket
Communication state restart
                              To App by intercepted
                              receive system call
• Create a new socket
                                                 Control                                 Control
• Copy control state in                          Timers,
                                                                    direct               Timers,
  checkpoint to socket structure                 Options,
                                                                    update               Options,
                                                                                         etc.
                                                 etc.
• Restore checkpointed send
  buffer data using the socket     copied_seq Rt+1      Sh
                                                       St+1        write_seq
                                                                   snd_una
                                                                                    Rt+1       Sh
                                        rcv_nxt Rt+1    Sh                           Rt+1      Sh
  write call
• Deliver checkpointed receive        Rh                      St       write()     Rh               St

  buffer data to application on                               .
                                                              .
  demand                              Rt
                                                              .
                                                                                    Rt
                                                                                                    Sh

                                     Recv                                         Recv          Send
                                     data                    Sh                   buffers       buffers
                                                       Send buffers
                                   Live Communication State                      Checkpoint State

                                                                               State for one socket
Existing Checkpointing mechanisms

• CryoPID
  – http://cryopid.berlios.de/
• BLCR (Berkeley Lab Checkpoint/Restart)
   – https://ftg.lbl.gov/projects/CheckpointRestart/
• DMTCP
  – http://dmtcp.sourceforge.net/
Implementation Considerations

• Checkpointing can be implemented in
  – kernel modifications + helpers in userspace
  – pure userspace
• Introduce a virtualization layer groups processes into specific
  states with private virtual name space
   – Intercepts system calls to expose only virtual identifiers (e.g.,
     vpid)
   – Preserves resource names and dependencies across
     migration
• Mechanism to checkpoint and restart states
   – User and kernel-level state
   – Primarily uses system call handlers
   – File system not saved or restored
DMTCP

• Distributed Multi-Threaded CheckPointing.
• Works with Linux Kernel 2.6.9 and later.
• Supports sequential and multi-threaded computations
  across single/multiple hosts.
• Entirely in user space (no kernel modules or root
  privilege).
   – Transparent (no recompiling, no re-linking).
• Written in Northeastern University and MIT and under
  active development since 2006.
• License: GNU LGPL (allows freely using and linking)
Process Structure
CT = DMTCP checkpoint thread
T = User Thread                   Coordinator           Signal (USR2)

                                                          DMTCP

                      CT                         CT
        Process 1                                         Process N
                    T1                          T1 T2
                               Network Socket

  dmtcp_checkpoint <EXE> # starts coordinator
  dmtcp_command –c                 # talks to coordinator
  dmtcp_restart ckpt_<EXE>-*.dmtcp
• Coordinator: a stateless synchronization server for the
  distributed checkpointing algorithm.
• Checkpoint/Restart performance related to size of memory,
  disk write speed, and synchronization.
How DMTCP works                                 (1/4)


       • MTCP : component for checkpoint single-process
       • SIGUSR2: Used internally from checkpoint thread to
         user threads.

Checkpoint thread


                                    CT
                                                     1. CT send SIGUSR2 to
                                                     each threads for suspend
                               T1        T2
2. Write checkpoint image
          to disk           User program


                                         3. Exit SIGUSR2 handler,
                                                 and resume.
How DMTCP works                           (2/4)


      • LD_PRELOAD: Transparently preloads checkpoint libraries
        `dmtcphijack.so` which installs libc wrappers and checkpointing
        code.
      • Wrappers: Only on less heavily used calls to libc
          – open, fork, exec, system, pipe, bind, listen,
            setsockopt, connect, accept, clone, close, ptsname,
            openlog, closelog, signal, sigaction, sigvec,
            sigblock, sigsetmask, sigprocmask, rt_sigprocmask,
            pthread_sigmask
          – Overhead is negligible.


                   int open(const char *path,   int open(const char *path,
                            int flags){                  int flags){
...                ...                          ...
fd = open(path,    funcs[_open](path, flags);   }
         flags);   ...
                   }
...                                                   libc.so
   User Program                dmtcphijack.so
How DMTCP works                          (3/4)


    • Additional wrappers when process id & thread id
      virtualization is enabled
        – getpid, getppid, gettid, tcgetpgrp,
          tcsetprgrp, getgrp, setpgrp, getsid,
          setsid, kill, tkill, tgkill, wait, waitpid,
          waitid, wait3, wait4



                                                  int getpid(){
                   int getpid(){                  ...
...                ...                            }
pid = getpid();    real_pid = funcs[_getpid]();
...                return pid_table[real_pid];
                   }
                                                    libc.so
    User Program
                        dmtcphijack.so
How DMTCP works                   (4/4)


• Checkpoint image compression on-the-fly (default).
• Currently only supports dynamically linking to libc.so.
  Support for static libc.a is feasible, but not
  implemented.
Checkpoint under DMTCP(1/7)

        • dmtcphijack.so and libmtcp.so present in executable’s
          memory.
               – dmtcp_checkpoint <EXE>




                 Coordinator


                                Connect to exist coordinator
                                or create a new coordinator

      CT            CT

    T1 T2         T1 T2

User program     User program
Checkpoint under DMTCP(2/7)

        • Ask coordinator process for checkpoint via
          dmtcp_command.
               – dmtcp_command -c
        • DMTCP also provides API to send command or query
          status

                 Coordinator    Send checkpoint
                                   command




      CT            CT
                                command
    T1 T2         T1 T2

User program     User program
Checkpoint under DMTCP(3/7)

        • Suspend user threads with SIGUSR2.



                              1. send command
                                  for prepare
                                  checkpoint
               Coordinator




      CT          CT                 2. CT send SIGUSR2 to
                                     each threads for suspend
    T1 T2       T1 T2

User program   User program
Checkpoint under DMTCP(4/7)

        • Pre-checkpoint stage
        • Synchronize every node and elect shared file
          descriptor leaders.
        • Drain kernel buffers and do network handshake with
          peers.
                               Wait until all node are ready.

               Coordinator
                                       1. Report all thread
                                    except CT are suspended



      CT          CT
                                         2. Drain buffers
    T1 T2       T1 T2

User program   User program
Checkpoint under DMTCP(5/7)

        • Write checkpoint to disk
               – One checkpoint file per process
               – ckpt_<EXE>_<uid>.dmtcp

                                          Wait until all node
                                         checkpoint are done

                 Coordinator




      CT             CT                       Write checkpoint to
                                                disk seprately
    T1 T2          T1 T2

User program      User program
Checkpoint under DMTCP(6/7)

        • Post-Checkpint stage
        • Refill kernel buffers


                                     Wait until all node
                                  post-checkpoint are done

               Coordinator




      CT          CT                      Refill buffer and
                                      re-handshake with peers.
    T1 T2       T1 T2

User program   User program
Checkpoint under DMTCP(7/7)

        • Resume user threads.




                                 Send resume command

               Coordinator




      CT          CT
                                          Resume!
    T1 T2       T1 T2

User program   User program
Restart under DMTCP(1/6)

• Restart Process loads in memory.
  – dmtcp_restart ckpt_<EXE>_<uid>.dmtcp




     Coordinator


                     1. Connect to exist coordinator
                     or create a new coordinator

        CT

                         2. Load process to memroy
     dmtcp_restart
Restart under DMTCP(2/6)

        • Fork user program




                Coordinator




      CT           CT



dmtcp_restart   dmtcp_restart
Restart under DMTCP(3/6)

        • Reopen files and recreate ptys
        • Recreate and reconnect sockets
        • Rearrange file descriptors to initial layout



                Coordinator          Wail all node recreate socket
                                             and reopen file


                                    1. Reopen file/ptys/sockets
      CT           CT

                                    2. Rearrange FD via dup2
dmtcp_restart   dmtcp_restart
Restart under DMTCP(4/6)

        • Restore memory content.
        • Restore stack status for checkpoint thread.
                                                FDs will preserved across execve!

                                dmtcp_restart
                                        execve
                Coordinator     mtcp_restart                   Coordinator
                                        mmap + magic!!
                                User program


      CT           CT                                 CT          CT



dmtcp_restart   dmtcp_restart                   User program   User program
Restart under DMTCP(5/6)

        • Restore other threads.
          – Recreate thread and restore stack and context.
          – Restore back to the post-checkpint stage
        • Refill kernel buffer

               Coordinator
                                   Wail all node restore done


                                     1. Memory and thread
                                        come back now!
      CT          CT

    T1 T2       T1 T2                   2. Refill buffers
User program   User program
Restart under DMTCP(6/6)

        • Resume user threads

                                stopthisthread
                                <sig-handler>
                                                  ...
                                <user_funcN>      while (mtcp_state_value(&thread -> state)



                                    ...
                                                           == ST_SUSPENDED) {
                                                    mtcp_state_futex (&(thread -> state),
                                <user_func2>                          FUTEX_WAIT,
                                                                      ST_SUSPENDED,
               Coordinator      <user_func1>                          NULL);
                                                  }
                              Thread Call Stack   ...




      CT          CT                                   Resume!

    T1 T2       T1 T2

User program   User program
DMTCP Workflow
                  Start with dmtcp
    Restart
                      wrapper




 Re-open FDs            Run


                                     Get checkpoint
                                       command
Restore memory    Pre-Checkpoint




Restore threads     Checkpoint

                                     Provide hook
                                        point!
                  Post-Checkpoint
OS Features supported by DMTCP

• Threads, mutexes/semaphores, fork, exec
• Shared memory (via mmap), TCP/IP sockets, UNIX
  domain sockets, pipes, ptys, terminal modes,
  ownership of controlling terminals, signal handlers,
  open and/or shared fds, I/O (including the readline
  library), parent-child process relationships, process id
  & thread id virtualization, session and process group
  ids, and more…
DMTCP/Android: Additional Features
                            (LGPL; separated from Android)
   • ARM Architecture support
      – Verified on Samsung Galaxy S2 + Android 4.0
   • Binder IPC
      – Client: supported
      – Server: partially supported

   • Ashmem: supported
   • Logger: supported
   • Properties: supported
   • Wakelocks: Not supported
Source code is available
https://github.com/0xlab/dmtcp-android
https://github.com/0xlab/android-checkpoint
Support new FD type in DMTCP

• In DMTCP, every FD has an associated `Connection`:
  – TcpConnection, FileConnection, PtyConnection

• Implement a new subclass of Connection if you want to
  support a new FD type for Android:
   ●   AshmemConnection, BinderConnection,
       LoggerConnection, PropertyConnection

• Also, implement the preCheckpoint,
  postCheckpint, and any others if needed.
Interface of Connection
class Connection {
   public:
     virtual void preCheckpoint (const dmtcp::vector<int>&,
                                  KernelBufferDrainer&);
     virtual void postCheckpoint (const dmtcp::vector<int>&,
                                   bool);
     virtual void restore (const dmtcp::vector<int>&,
                           ConnectionRewirer *);
     virtual bool isDupConnection (const Connection&,
                                   dmtcp::ConnectionToFds&);
     virtual void doLocking (const dmtcp::vector<int>&);
     virtual void saveOptions (const dmtcp::vector<int>&);
     virtual void restoreOptions (const dmtcp::vector<int>& );
     virtual void doSendHandshakes (const dmtcp::vector<int>&,
                                    const dmtcp::UniquePid&);
     virtual void doRecvHandshakes (const dmtcp::vector<int>&,
                                    const dmtcp::UniquePid&);
     virtual void restartDup2 (int, int);
   protected:
     virtual void serializeSubClass (jalib::JBinarySerializer&);
};
Android Binder support for DMTCP

• BinderConnection
   – Reopen /dev/binder and reset ioctl parameters
   – Restore the mmap region

• Hijack the whole libbinder
   – Prevent libbinder from interpreting data twice
   – Implement necessary DMTCP hooks: preCheckpoint,
     postCheckpoint, postRestart
      • Re-initialize libbinder in postRestart
• The server part is partially supported because binder
  server is calling a blocked ioctl and blocking the whole
  checkpoint process.
   – We implement an early checkpoint stage to suspend
     such kind of threads.
More extensions in DMTCP/Android

 • Improve the hook system in DMTCP
    – Original design only allows one set hook function.
    – Allow more than one set hook function in
      DMTCP/Android.
 • Implement per thread callback hook
    – Restore the DVM internal thread info
 • Add barrier and synchronize mechanisms to DMTCP
    – In order to make precise program checkpointing.
Android specific modifications

• Reorder code in framework
  – registerZygoteSocket()
     • The socket is inherited from the parent process `init`,
       which implies we can not handle it in DMTCP.
  – Move few initializations later than the checkpoint process
    since the current binder support is incomplete.

• Reserve the ashmem's file descriptor
  – Original behavior is to close the fd after mmap
  – DMTCP binds connection to one fd, so the connection will be
    destroyed if that fd is closed.
• Implement the missing PThread function in bionic libc
  – pthread_tryjoin_np is required by DMTCP,
    but it s not implemented in original bionic.
Technical Issues when modifying
•   ARM Architecture support is incomplete.
                                            DMTCP
    – We are going to contribute back to upstream.
• Different TLS implementation semantics between glibc and
  bionic libc
   – DMTCP/Android follows the techniques used in Android´s
     OpenGL ES package which links and defers to the slot of
     TLS in bionic libc. Not elegant, but it works
• PThread implementation expectation is quite different
   – AOSP master branch is merging libc from NetBSD, so it
     should be better for compatibility.
• Behavior of dynamic linker differs a lot in bionic libc.
• Flags in dlopen() is not really functional.
• The way to find symbol in bionic libc differs: weak symbol
Checkpoint for Zygote
• Experiment environment:
   – Android-x86 ICS emulated by VirtualBox
   – Host: Thinkpad x200 (Intel Core 2 Due @ 2.4 GHz)

                       with gzip          without gzip

                                   ~10s             ~5.5s
  Checkpoint time

                               ~0.5s                ~0.2s
  Restart time

                                   ~3M              ~17M
  Image size
Observations from logcat
--------- beginning of /dev/log/system                                   --------- beginning of /dev/log/system
I/Vold ( 1270): Vold 2.1 (the revenge) firing up                         I/Vold ( 1270): Vold 2.1 (the revenge) firing up
                                                                         D/Vold ( 1270): Volume usb state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 1270): Volume usb state changing -1 (Initializing) -> 0 (No-Media)
I/Netd ( 1271): Netd 1.0 starting                                        I/Netd ( 1271): Netd 1.0 starting
I/      ( 1275): ServiceManager: 0x8062b50                               I/      ( 1275): ServiceManager: 0x8062b50
I/      ( 1276): ServiceManager: 0x804fb98                               I/      ( 1276): ServiceManager: 0x804fb98
                                                                         I/AudioFlinger( 1276): Loaded primary audio interface from LEGACY Audio HW
I/AudioFlinger( 1276): Loaded primary audio interface from LEGACY Audio HW HAL (audio)
I/AudioFlinger( 1276): Using 'LEGACY Audio HW HAL' (audio.primary) as I/AudioFlinger( 1276): Using 'LEGACY Audio HW HAL' (audio.primary) as the
                                                                          the primary audio interface
...                                                                      ….
D/AudioHardware( 1276): ### setVoiceVolume: 1.000000                     D/AudioHardware( 1276): ### setVoiceVolume: 1.000000
                                                                         I/AudioPolicyService( 1276): [1276]Loaded audio policy from LEGACY Audio P
I/AudioPolicyService( 1276): [1276]Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)
E/BatteryService( 1382): usbOnlinePath not found                         D/dalvikvm( 1373): GC_EXPLICIT freed 14K, 1% free 6418K/6467K, paused 0
D/AndroidRuntime( 1902):                                                 D/dalvikvm( 1373): GC_EXPLICIT freed 5K, 1% free 6412K/6467K, paused 0m
                                                                         D/dalvikvm( 1373): GC_EXPLICIT freed <1K, 1% free 6412K/6467K, paused 0
D/AndroidRuntime( 1902): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 1902): CheckJNI is ON                                  I/dalvikvm( 1373): System server process 1382 has been created
I/SamplingProfilerIntegration( 1902): Profiling disabled.
I/Zygote ( 1902): Preloading classes...
D/dalvikvm( 1902): GC_EXPLICIT freed 35K, 85% free 399K/2560K, paused 0ms+0ms
...
I/Zygote ( 1902): ...preloaded 379 resources in 548ms.
D/dalvikvm( 1902): GC_EXPLICIT freed 20K, 1% free 6417K/6467K, paused 0ms+0ms
I/Zygote ( 1902): ...preloaded 31 resources in 13ms.
D/dalvikvm( 1902): GC_EXPLICIT freed 14K, 1% free 6418K/6467K, paused 0ms+0ms
D/dalvikvm( 1902): GC_EXPLICIT freed 5K, 1% free 6412K/6467K, paused 0ms+0ms
D/dalvikvm( 1902): GC_EXPLICIT freed <1K, 1% free 6412K/6467K, paused 0ms+2ms
I/dalvikvm( 1902): System server process 1911 has been created



  Normal bootup log message                                                 Bootup log message with restart
Android Boottime with DMTCP
              1     2     3      4     5     6    7     8     9    10    avg

           27.96   27.95 32.89 26.59 32.33 32.36 33.22 32.99 36.47 32.85 31.56
Boottime


Boottime   15.02 15.86 15.13 14.88 14.57 14.43 14.73 14.22 13.97 14.61   14.74
with DMTCP
(w/ gzip)
Boottime   14.98 15.13 14.61 13.90 14.72 14.84 15.46 15.06 15.32 15.39   14.94
with DMTCP
(w/o gzip)




  Measured by uptime in onStart() of Launcher2
Reversible Debugger based on DMTCP

• URDB is a universal reversible debugger that can add
  reversibility gained through the use of DMTCP.
• A user debugging with gdb would then ask URDB to go
  back to a point in time to when:
   – the expression had a correct value
   – the next statement would cause the expression to
     take on an incorrect value.
• Project page: http://sourceforge.net/projects/urdb/
Reversible Debugger using
             Checkpointing
Reference
• “DMTCP: An New Linux Checkpointing Mechanism for Vanilla
  Universe Job”, Condor Project, University of
  Wisconsin-Madison
• “Checkpointing using DMTCP, Condor, Matlab and FReD”,
  Gene Cooperman, Northeastern University, Boston
• URDB: Universal Reversible Debugger
  http://arxiv.org/abs/0910.5046
• Cruz: Application-Transparent Distributed Checkpoint-Restart
  on Standard Operating Systems, G. (John) Janakiraman, Jose
  Renato Santos, Dinesh Subhraveti, Yoshio Turner, HP Labs
http://0xlab.org

Weitere ähnliche Inhalte

Was ist angesagt?

F9: A Secure and Efficient Microkernel Built for Deeply Embedded Systems
F9: A Secure and Efficient Microkernel Built for Deeply Embedded SystemsF9: A Secure and Efficient Microkernel Built for Deeply Embedded Systems
F9: A Secure and Efficient Microkernel Built for Deeply Embedded SystemsNational Cheng Kung University
 
Learning, Analyzing and Protecting Android with TOMOYO Linux (JLS2009)
Learning, Analyzing and Protecting Android with TOMOYO Linux (JLS2009)Learning, Analyzing and Protecting Android with TOMOYO Linux (JLS2009)
Learning, Analyzing and Protecting Android with TOMOYO Linux (JLS2009)Toshiharu Harada, Ph.D
 
Android graphic system (SurfaceFlinger) : Design Pattern's perspective
Android graphic system (SurfaceFlinger) : Design Pattern's perspectiveAndroid graphic system (SurfaceFlinger) : Design Pattern's perspective
Android graphic system (SurfaceFlinger) : Design Pattern's perspectiveBin Chen
 
Linaro Connect 2016 (BKK16) - Introduction to LISA
Linaro Connect 2016 (BKK16) - Introduction to LISALinaro Connect 2016 (BKK16) - Introduction to LISA
Linaro Connect 2016 (BKK16) - Introduction to LISAPatrick Bellasi
 
What's LUM Got To Do with It: Deployment Considerations for Linux User Manage...
What's LUM Got To Do with It: Deployment Considerations for Linux User Manage...What's LUM Got To Do with It: Deployment Considerations for Linux User Manage...
What's LUM Got To Do with It: Deployment Considerations for Linux User Manage...Novell
 
Apache Hadoop India Summit 2011 talk "Profiling Application Performance" by U...
Apache Hadoop India Summit 2011 talk "Profiling Application Performance" by U...Apache Hadoop India Summit 2011 talk "Profiling Application Performance" by U...
Apache Hadoop India Summit 2011 talk "Profiling Application Performance" by U...Yahoo Developer Network
 
Performance Profiling of Virtual Machines
Performance Profiling of Virtual MachinesPerformance Profiling of Virtual Machines
Performance Profiling of Virtual MachinesJiaqing Du
 
ScalableCore System: A Scalable Many-core Simulator by Employing Over 100 FPGAs
ScalableCore System: A Scalable Many-core Simulator by Employing Over 100 FPGAsScalableCore System: A Scalable Many-core Simulator by Employing Over 100 FPGAs
ScalableCore System: A Scalable Many-core Simulator by Employing Over 100 FPGAsShinya Takamaeda-Y
 
Performance Profiling in a Virtualized Environment
Performance Profiling in a Virtualized EnvironmentPerformance Profiling in a Virtualized Environment
Performance Profiling in a Virtualized EnvironmentJiaqing Du
 
Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...
Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...
Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...peknap
 

Was ist angesagt? (20)

ARM and SoC Traning Part I -- Overview
ARM and SoC Traning Part I -- OverviewARM and SoC Traning Part I -- Overview
ARM and SoC Traning Part I -- Overview
 
Dvm
DvmDvm
Dvm
 
Learn C Programming Language by Using GDB
Learn C Programming Language by Using GDBLearn C Programming Language by Using GDB
Learn C Programming Language by Using GDB
 
F9: A Secure and Efficient Microkernel Built for Deeply Embedded Systems
F9: A Secure and Efficient Microkernel Built for Deeply Embedded SystemsF9: A Secure and Efficient Microkernel Built for Deeply Embedded Systems
F9: A Secure and Efficient Microkernel Built for Deeply Embedded Systems
 
Android IPC Mechanism
Android IPC MechanismAndroid IPC Mechanism
Android IPC Mechanism
 
Implement Runtime Environments for HSA using LLVM
Implement Runtime Environments for HSA using LLVMImplement Runtime Environments for HSA using LLVM
Implement Runtime Environments for HSA using LLVM
 
Learning, Analyzing and Protecting Android with TOMOYO Linux (JLS2009)
Learning, Analyzing and Protecting Android with TOMOYO Linux (JLS2009)Learning, Analyzing and Protecting Android with TOMOYO Linux (JLS2009)
Learning, Analyzing and Protecting Android with TOMOYO Linux (JLS2009)
 
Android graphic system (SurfaceFlinger) : Design Pattern's perspective
Android graphic system (SurfaceFlinger) : Design Pattern's perspectiveAndroid graphic system (SurfaceFlinger) : Design Pattern's perspective
Android graphic system (SurfaceFlinger) : Design Pattern's perspective
 
Linaro Connect 2016 (BKK16) - Introduction to LISA
Linaro Connect 2016 (BKK16) - Introduction to LISALinaro Connect 2016 (BKK16) - Introduction to LISA
Linaro Connect 2016 (BKK16) - Introduction to LISA
 
What's LUM Got To Do with It: Deployment Considerations for Linux User Manage...
What's LUM Got To Do with It: Deployment Considerations for Linux User Manage...What's LUM Got To Do with It: Deployment Considerations for Linux User Manage...
What's LUM Got To Do with It: Deployment Considerations for Linux User Manage...
 
Embedded Virtualization applied in Mobile Devices
Embedded Virtualization applied in Mobile DevicesEmbedded Virtualization applied in Mobile Devices
Embedded Virtualization applied in Mobile Devices
 
Apache Hadoop India Summit 2011 talk "Profiling Application Performance" by U...
Apache Hadoop India Summit 2011 talk "Profiling Application Performance" by U...Apache Hadoop India Summit 2011 talk "Profiling Application Performance" by U...
Apache Hadoop India Summit 2011 talk "Profiling Application Performance" by U...
 
Performance Profiling of Virtual Machines
Performance Profiling of Virtual MachinesPerformance Profiling of Virtual Machines
Performance Profiling of Virtual Machines
 
XS Boston 2008 Security
XS Boston 2008 SecurityXS Boston 2008 Security
XS Boston 2008 Security
 
ScalableCore System: A Scalable Many-core Simulator by Employing Over 100 FPGAs
ScalableCore System: A Scalable Many-core Simulator by Employing Over 100 FPGAsScalableCore System: A Scalable Many-core Simulator by Employing Over 100 FPGAs
ScalableCore System: A Scalable Many-core Simulator by Employing Over 100 FPGAs
 
Performance Profiling in a Virtualized Environment
Performance Profiling in a Virtualized EnvironmentPerformance Profiling in a Virtualized Environment
Performance Profiling in a Virtualized Environment
 
L4 Microkernel :: Design Overview
L4 Microkernel :: Design OverviewL4 Microkernel :: Design Overview
L4 Microkernel :: Design Overview
 
I/O Scalability in Xen
I/O Scalability in XenI/O Scalability in Xen
I/O Scalability in Xen
 
Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...
Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...
Solving Real-Time Scheduling Problems With RT_PREEMPT and Deadline-Based Sche...
 
Chen Haibo
Chen HaiboChen Haibo
Chen Haibo
 

Ähnlich wie Implement Checkpointing for Android (ELCE2012)

Cruz: Application-Transparent Distributed Checkpoint-Restart on Standard Oper...
Cruz:Application-Transparent Distributed Checkpoint-Restart on Standard Oper...Cruz:Application-Transparent Distributed Checkpoint-Restart on Standard Oper...
Cruz: Application-Transparent Distributed Checkpoint-Restart on Standard Oper...Mark J. Feldman
 
Springone2gx 2014 Reactive Streams and Reactor
Springone2gx 2014 Reactive Streams and ReactorSpringone2gx 2014 Reactive Streams and Reactor
Springone2gx 2014 Reactive Streams and ReactorStéphane Maldini
 
XenTT: Deterministic Systems Analysis in Xen
XenTT: Deterministic Systems Analysis in XenXenTT: Deterministic Systems Analysis in Xen
XenTT: Deterministic Systems Analysis in XenThe Linux Foundation
 
Thoughts on consistency models
Thoughts on consistency modelsThoughts on consistency models
Thoughts on consistency modelsrogerbodamer
 
From a Kafkaesque Story to The Promised Land at LivePerson
From a Kafkaesque Story to The Promised Land at LivePersonFrom a Kafkaesque Story to The Promised Land at LivePerson
From a Kafkaesque Story to The Promised Land at LivePersonLivePerson
 
Realtime Statistics based on Apache Storm and RocketMQ
Realtime Statistics based on Apache Storm and RocketMQRealtime Statistics based on Apache Storm and RocketMQ
Realtime Statistics based on Apache Storm and RocketMQXin Wang
 
#lspe: Dynamic Scaling
#lspe: Dynamic Scaling #lspe: Dynamic Scaling
#lspe: Dynamic Scaling steveshah
 
Realtime olap architecture in apache kylin 3.0
Realtime olap architecture in apache kylin 3.0Realtime olap architecture in apache kylin 3.0
Realtime olap architecture in apache kylin 3.0Shi Shao Feng
 
Perfomance tuning on Go 2.0
Perfomance tuning on Go 2.0Perfomance tuning on Go 2.0
Perfomance tuning on Go 2.0Yogi Kulkarni
 
Always On - Wydajność i bezpieczeństwo naszych danych - High Availability SQL...
Always On - Wydajność i bezpieczeństwo naszych danych - High Availability SQL...Always On - Wydajność i bezpieczeństwo naszych danych - High Availability SQL...
Always On - Wydajność i bezpieczeństwo naszych danych - High Availability SQL...SQLExpert.pl
 
Architectures with Windows Azure
Architectures with Windows AzureArchitectures with Windows Azure
Architectures with Windows AzureDamir Dobric
 
Co nowego w SQL Server 11 – Denali CTP1 - Grzegorz Stolecki, Łukasz Grala i K...
Co nowego w SQL Server 11 – Denali CTP1 - Grzegorz Stolecki, Łukasz Grala i K...Co nowego w SQL Server 11 – Denali CTP1 - Grzegorz Stolecki, Łukasz Grala i K...
Co nowego w SQL Server 11 – Denali CTP1 - Grzegorz Stolecki, Łukasz Grala i K...Polish SQL Server User Group
 
Exactly-once Stream Processing Done Right with Matthias J Sax
Exactly-once Stream Processing Done Right with Matthias J SaxExactly-once Stream Processing Done Right with Matthias J Sax
Exactly-once Stream Processing Done Right with Matthias J SaxHostedbyConfluent
 
Red Hat Storage Server Replication Past, Present, & Future
Red Hat Storage Server Replication Past, Present, & FutureRed Hat Storage Server Replication Past, Present, & Future
Red Hat Storage Server Replication Past, Present, & FutureRed_Hat_Storage
 
Red hat storage server replication past, present, & future
Red hat storage server replication  past, present, & futureRed hat storage server replication  past, present, & future
Red hat storage server replication past, present, & futureTaline Felix
 
Data Replication in Distributed System
Data Replication in  Distributed SystemData Replication in  Distributed System
Data Replication in Distributed SystemEhsan Hessami
 
From a kafkaesque story to The Promised Land
From a kafkaesque story to The Promised LandFrom a kafkaesque story to The Promised Land
From a kafkaesque story to The Promised LandRan Silberman
 
Parsing and Type checking all 2^10000 configurations of the Linux kernel
Parsing and Type checking all 2^10000 configurations of the Linux kernelParsing and Type checking all 2^10000 configurations of the Linux kernel
Parsing and Type checking all 2^10000 configurations of the Linux kernelchk49
 
The Pill for Your Migration Hell
The Pill for Your Migration HellThe Pill for Your Migration Hell
The Pill for Your Migration HellDatabricks
 

Ähnlich wie Implement Checkpointing for Android (ELCE2012) (20)

Cruz: Application-Transparent Distributed Checkpoint-Restart on Standard Oper...
Cruz:Application-Transparent Distributed Checkpoint-Restart on Standard Oper...Cruz:Application-Transparent Distributed Checkpoint-Restart on Standard Oper...
Cruz: Application-Transparent Distributed Checkpoint-Restart on Standard Oper...
 
Springone2gx 2014 Reactive Streams and Reactor
Springone2gx 2014 Reactive Streams and ReactorSpringone2gx 2014 Reactive Streams and Reactor
Springone2gx 2014 Reactive Streams and Reactor
 
XenTT: Deterministic Systems Analysis in Xen
XenTT: Deterministic Systems Analysis in XenXenTT: Deterministic Systems Analysis in Xen
XenTT: Deterministic Systems Analysis in Xen
 
Thoughts on consistency models
Thoughts on consistency modelsThoughts on consistency models
Thoughts on consistency models
 
From a Kafkaesque Story to The Promised Land at LivePerson
From a Kafkaesque Story to The Promised Land at LivePersonFrom a Kafkaesque Story to The Promised Land at LivePerson
From a Kafkaesque Story to The Promised Land at LivePerson
 
Realtime Statistics based on Apache Storm and RocketMQ
Realtime Statistics based on Apache Storm and RocketMQRealtime Statistics based on Apache Storm and RocketMQ
Realtime Statistics based on Apache Storm and RocketMQ
 
#lspe: Dynamic Scaling
#lspe: Dynamic Scaling #lspe: Dynamic Scaling
#lspe: Dynamic Scaling
 
Realtime olap architecture in apache kylin 3.0
Realtime olap architecture in apache kylin 3.0Realtime olap architecture in apache kylin 3.0
Realtime olap architecture in apache kylin 3.0
 
Perfomance tuning on Go 2.0
Perfomance tuning on Go 2.0Perfomance tuning on Go 2.0
Perfomance tuning on Go 2.0
 
Always On - Wydajność i bezpieczeństwo naszych danych - High Availability SQL...
Always On - Wydajność i bezpieczeństwo naszych danych - High Availability SQL...Always On - Wydajność i bezpieczeństwo naszych danych - High Availability SQL...
Always On - Wydajność i bezpieczeństwo naszych danych - High Availability SQL...
 
Architectures with Windows Azure
Architectures with Windows AzureArchitectures with Windows Azure
Architectures with Windows Azure
 
Co nowego w SQL Server 11 – Denali CTP1 - Grzegorz Stolecki, Łukasz Grala i K...
Co nowego w SQL Server 11 – Denali CTP1 - Grzegorz Stolecki, Łukasz Grala i K...Co nowego w SQL Server 11 – Denali CTP1 - Grzegorz Stolecki, Łukasz Grala i K...
Co nowego w SQL Server 11 – Denali CTP1 - Grzegorz Stolecki, Łukasz Grala i K...
 
Exactly-once Stream Processing Done Right with Matthias J Sax
Exactly-once Stream Processing Done Right with Matthias J SaxExactly-once Stream Processing Done Right with Matthias J Sax
Exactly-once Stream Processing Done Right with Matthias J Sax
 
Red Hat Storage Server Replication Past, Present, & Future
Red Hat Storage Server Replication Past, Present, & FutureRed Hat Storage Server Replication Past, Present, & Future
Red Hat Storage Server Replication Past, Present, & Future
 
Red hat storage server replication past, present, & future
Red hat storage server replication  past, present, & futureRed hat storage server replication  past, present, & future
Red hat storage server replication past, present, & future
 
XS Oracle 2009 Just Run It
XS Oracle 2009 Just Run ItXS Oracle 2009 Just Run It
XS Oracle 2009 Just Run It
 
Data Replication in Distributed System
Data Replication in  Distributed SystemData Replication in  Distributed System
Data Replication in Distributed System
 
From a kafkaesque story to The Promised Land
From a kafkaesque story to The Promised LandFrom a kafkaesque story to The Promised Land
From a kafkaesque story to The Promised Land
 
Parsing and Type checking all 2^10000 configurations of the Linux kernel
Parsing and Type checking all 2^10000 configurations of the Linux kernelParsing and Type checking all 2^10000 configurations of the Linux kernel
Parsing and Type checking all 2^10000 configurations of the Linux kernel
 
The Pill for Your Migration Hell
The Pill for Your Migration HellThe Pill for Your Migration Hell
The Pill for Your Migration Hell
 

Mehr von National Cheng Kung University

PyPy's approach to construct domain-specific language runtime
PyPy's approach to construct domain-specific language runtimePyPy's approach to construct domain-specific language runtime
PyPy's approach to construct domain-specific language runtimeNational Cheng Kung University
 
進階嵌入式作業系統設計與實做 (2015 年秋季 ) 課程說明
進階嵌入式作業系統設計與實做 (2015 年秋季 ) 課程說明進階嵌入式作業系統設計與實做 (2015 年秋季 ) 課程說明
進階嵌入式作業系統設計與實做 (2015 年秋季 ) 課程說明National Cheng Kung University
 
給自己更好未來的 3 個練習:嵌入式作業系統設計、實做,與移植 (2015 年春季 ) 課程說明
給自己更好未來的 3 個練習:嵌入式作業系統設計、實做,與移植 (2015 年春季 ) 課程說明給自己更好未來的 3 個練習:嵌入式作業系統設計、實做,與移植 (2015 年春季 ) 課程說明
給自己更好未來的 3 個練習:嵌入式作業系統設計、實做,與移植 (2015 年春季 ) 課程說明National Cheng Kung University
 
進階嵌入式系統開發與實做 (2014 年秋季 ) 課程說明
進階嵌入式系統開發與實做 (2014 年秋季 ) 課程說明進階嵌入式系統開發與實做 (2014 年秋季 ) 課程說明
進階嵌入式系統開發與實做 (2014 年秋季 ) 課程說明National Cheng Kung University
 
Develop Your Own Operating Systems using Cheap ARM Boards
Develop Your Own Operating Systems using Cheap ARM BoardsDevelop Your Own Operating Systems using Cheap ARM Boards
Develop Your Own Operating Systems using Cheap ARM BoardsNational Cheng Kung University
 
Lecture notice about Embedded Operating System Design and Implementation
Lecture notice about Embedded Operating System Design and ImplementationLecture notice about Embedded Operating System Design and Implementation
Lecture notice about Embedded Operating System Design and ImplementationNational Cheng Kung University
 
中輟生談教育: 完全用開放原始碼軟體進行 嵌入式系統教學
中輟生談教育: 完全用開放原始碼軟體進行 嵌入式系統教學中輟生談教育: 完全用開放原始碼軟體進行 嵌入式系統教學
中輟生談教育: 完全用開放原始碼軟體進行 嵌入式系統教學National Cheng Kung University
 
進階嵌入式系統開發與實作 (2013 秋季班 ) 課程說明
進階嵌入式系統開發與實作 (2013 秋季班 ) 課程說明進階嵌入式系統開發與實作 (2013 秋季班 ) 課程說明
進階嵌入式系統開發與實作 (2013 秋季班 ) 課程說明National Cheng Kung University
 

Mehr von National Cheng Kung University (20)

PyPy's approach to construct domain-specific language runtime
PyPy's approach to construct domain-specific language runtimePyPy's approach to construct domain-specific language runtime
PyPy's approach to construct domain-specific language runtime
 
Making Linux do Hard Real-time
Making Linux do Hard Real-timeMaking Linux do Hard Real-time
Making Linux do Hard Real-time
 
2016 年春季嵌入式作業系統課程說明
2016 年春季嵌入式作業系統課程說明2016 年春季嵌入式作業系統課程說明
2016 年春季嵌入式作業系統課程說明
 
Interpreter, Compiler, JIT from scratch
Interpreter, Compiler, JIT from scratchInterpreter, Compiler, JIT from scratch
Interpreter, Compiler, JIT from scratch
 
進階嵌入式作業系統設計與實做 (2015 年秋季 ) 課程說明
進階嵌入式作業系統設計與實做 (2015 年秋季 ) 課程說明進階嵌入式作業系統設計與實做 (2015 年秋季 ) 課程說明
進階嵌入式作業系統設計與實做 (2015 年秋季 ) 課程說明
 
Construct an Efficient and Secure Microkernel for IoT
Construct an Efficient and Secure Microkernel for IoTConstruct an Efficient and Secure Microkernel for IoT
Construct an Efficient and Secure Microkernel for IoT
 
The Internals of "Hello World" Program
The Internals of "Hello World" ProgramThe Internals of "Hello World" Program
The Internals of "Hello World" Program
 
How A Compiler Works: GNU Toolchain
How A Compiler Works: GNU ToolchainHow A Compiler Works: GNU Toolchain
How A Compiler Works: GNU Toolchain
 
Virtual Machine Constructions for Dummies
Virtual Machine Constructions for DummiesVirtual Machine Constructions for Dummies
Virtual Machine Constructions for Dummies
 
給自己更好未來的 3 個練習:嵌入式作業系統設計、實做,與移植 (2015 年春季 ) 課程說明
給自己更好未來的 3 個練習:嵌入式作業系統設計、實做,與移植 (2015 年春季 ) 課程說明給自己更好未來的 3 個練習:嵌入式作業系統設計、實做,與移植 (2015 年春季 ) 課程說明
給自己更好未來的 3 個練習:嵌入式作業系統設計、實做,與移植 (2015 年春季 ) 課程說明
 
從線上售票看作業系統設計議題
從線上售票看作業系統設計議題從線上售票看作業系統設計議題
從線上售票看作業系統設計議題
 
進階嵌入式系統開發與實做 (2014 年秋季 ) 課程說明
進階嵌入式系統開發與實做 (2014 年秋季 ) 課程說明進階嵌入式系統開發與實做 (2014 年秋季 ) 課程說明
進階嵌入式系統開發與實做 (2014 年秋季 ) 課程說明
 
Making Linux do Hard Real-time
Making Linux do Hard Real-timeMaking Linux do Hard Real-time
Making Linux do Hard Real-time
 
Priority Inversion on Mars
Priority Inversion on MarsPriority Inversion on Mars
Priority Inversion on Mars
 
Develop Your Own Operating Systems using Cheap ARM Boards
Develop Your Own Operating Systems using Cheap ARM BoardsDevelop Your Own Operating Systems using Cheap ARM Boards
Develop Your Own Operating Systems using Cheap ARM Boards
 
Lecture notice about Embedded Operating System Design and Implementation
Lecture notice about Embedded Operating System Design and ImplementationLecture notice about Embedded Operating System Design and Implementation
Lecture notice about Embedded Operating System Design and Implementation
 
中輟生談教育: 完全用開放原始碼軟體進行 嵌入式系統教學
中輟生談教育: 完全用開放原始碼軟體進行 嵌入式系統教學中輟生談教育: 完全用開放原始碼軟體進行 嵌入式系統教學
中輟生談教育: 完全用開放原始碼軟體進行 嵌入式系統教學
 
Open Source from Legend, Business, to Ecosystem
Open Source from Legend, Business, to EcosystemOpen Source from Legend, Business, to Ecosystem
Open Source from Legend, Business, to Ecosystem
 
Summer Project: Microkernel (2013)
Summer Project: Microkernel (2013)Summer Project: Microkernel (2013)
Summer Project: Microkernel (2013)
 
進階嵌入式系統開發與實作 (2013 秋季班 ) 課程說明
進階嵌入式系統開發與實作 (2013 秋季班 ) 課程說明進階嵌入式系統開發與實作 (2013 秋季班 ) 課程說明
進階嵌入式系統開發與實作 (2013 秋季班 ) 課程說明
 

Kürzlich hochgeladen

UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UbiTrack UK
 
AI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarAI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarPrecisely
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...Aggregage
 
Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1DianaGray10
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Websitedgelyza
 
Building AI-Driven Apps Using Semantic Kernel.pptx
Building AI-Driven Apps Using Semantic Kernel.pptxBuilding AI-Driven Apps Using Semantic Kernel.pptx
Building AI-Driven Apps Using Semantic Kernel.pptxUdaiappa Ramachandran
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024SkyPlanner
 
20230202 - Introduction to tis-py
20230202 - Introduction to tis-py20230202 - Introduction to tis-py
20230202 - Introduction to tis-pyJamie (Taka) Wang
 
Linked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesLinked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesDavid Newbury
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Will Schroeder
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxMatsuo Lab
 
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDELiveplex
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024D Cloud Solutions
 
Building Your Own AI Instance (TBLC AI )
Building Your Own AI Instance (TBLC AI )Building Your Own AI Instance (TBLC AI )
Building Your Own AI Instance (TBLC AI )Brian Pichman
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationIES VE
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfDianaGray10
 
Comparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioComparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioChristian Posta
 
NIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopNIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopBachir Benyammi
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsSafe Software
 

Kürzlich hochgeladen (20)

UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
UWB Technology for Enhanced Indoor and Outdoor Positioning in Physiological M...
 
AI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarAI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity Webinar
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
 
Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Website
 
Building AI-Driven Apps Using Semantic Kernel.pptx
Building AI-Driven Apps Using Semantic Kernel.pptxBuilding AI-Driven Apps Using Semantic Kernel.pptx
Building AI-Driven Apps Using Semantic Kernel.pptx
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024
 
20230202 - Introduction to tis-py
20230202 - Introduction to tis-py20230202 - Introduction to tis-py
20230202 - Introduction to tis-py
 
Linked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesLinked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond Ontologies
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptx
 
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024
 
Building Your Own AI Instance (TBLC AI )
Building Your Own AI Instance (TBLC AI )Building Your Own AI Instance (TBLC AI )
Building Your Own AI Instance (TBLC AI )
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
 
Comparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and IstioComparing Sidecar-less Service Mesh from Cilium and Istio
Comparing Sidecar-less Service Mesh from Cilium and Istio
 
NIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopNIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 Workshop
 
201610817 - edge part1
201610817 - edge part1201610817 - edge part1
201610817 - edge part1
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
 

Implement Checkpointing for Android (ELCE2012)

  • 1. Implement Checkpointing for Android (to speed up boot time and development process) Jim Huang ( 黃敬群 ) <jserv@0xlab.org> Kito Cheng ( 程皇嘉 ) <kito@0xlab.org> Developer, 0xlab Nov 5, 2012 ! Embedded Linux Conference Europe
  • 2. Rights to copy © Copyright 2012 0xlab http://0xlab.org/ contact@0xlab.org Attribution – ShareAlike 3.0 Corrections, suggestions, contributions and translations You are free are welcome! to copy, distribute, display, and perform the work to make derivative works Latest update: Nov 21, 2012 to make commercial use of the work Under the following conditions Attribution. You must give the original author credit. Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. For any reuse or distribution, you must make clear to others the license terms of this work. Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. License text: http://creativecommons.org/licenses/by-sa/3.0/legalcode
  • 3. Basic Idea: Process Migration • Process Migration (in past applications) – Distributed Load Balancing – Efficient Resource Utilization • Crash Recovery and Rollback Transaction – Useful to system admin Processes Checkpoint Processes Processes Library Library Library TCP/IP TCP/IP TCP/IP Node Node Node Communication Channel
  • 4. Checkpointing • From Wikipedia: – … is a technique for inserting fault tolerance into computing systems. It basically consists of storing a snapshot of the current application state, and later on, use it for restarting the execution in case of failure. • Used in distributed shared memory systems • Even used in reversible debugger • Different from virtual machine level snapshot/resume mechanisms – Checkpointing emphasizes on process level.
  • 5. Ideas about Checkpointing for Android • Resume to stored state for faster Android boot time • Better product field trial experience due to regular checkpointing • Deploy problematic states for engineering analysis and debugging transparently • Q&A stress test purpose
  • 6. Expectations of Checkpointing • Application-transparent – supports applications without modifications or recompilation • Supports a broad class of applications – Databases – parallel / MPI apps – desktop apps • Comprehensive support for user-level state, kernel-level state, and distributed computation and communication state • Supported on unmodified Linux kernel – checkpoint-restart should be integrated by addons
  • 7. Challenges in checkpoint and restore • Network stack will continue to execute even after application processes are stopped • No system call interface to read or write control state • No system call interface to read send socket buffers • No system call interface to write receive socket buffers • Consistency of control state and socket buffer state
  • 8. Communication state checkpoint • Acquire network stack locks to freeze TCP processing Control Control direct • Save receive buffers using Timers, Options, access Timers, Options, socket receive system call in etc. etc. peek mode copied_seq Rh St+1 write_seq Rt+1 Rh X X St+1 Sh • Save send buffers by walking rcv_nxt Rt+1 Sh snd_una Rt+1 Sh kernel structures direct Rh St access Rh St • Copy control state from kernel structures . . . . receive() . . Sh Rt • Modify two sequence numbers Recv Send in saved state to reflect empty Rt Sh buffers buffers Recv buffers Send buffers socket buffers Live Communication State Checkpoint State State for one socket
  • 9. Communication state restart To App by intercepted receive system call • Create a new socket Control Control • Copy control state in Timers, direct Timers, checkpoint to socket structure Options, update Options, etc. etc. • Restore checkpointed send buffer data using the socket copied_seq Rt+1 Sh St+1 write_seq snd_una Rt+1 Sh rcv_nxt Rt+1 Sh Rt+1 Sh write call • Deliver checkpointed receive Rh St write() Rh St buffer data to application on . . demand Rt . Rt Sh Recv Recv Send data Sh buffers buffers Send buffers Live Communication State Checkpoint State State for one socket
  • 10. Existing Checkpointing mechanisms • CryoPID – http://cryopid.berlios.de/ • BLCR (Berkeley Lab Checkpoint/Restart) – https://ftg.lbl.gov/projects/CheckpointRestart/ • DMTCP – http://dmtcp.sourceforge.net/
  • 11. Implementation Considerations • Checkpointing can be implemented in – kernel modifications + helpers in userspace – pure userspace • Introduce a virtualization layer groups processes into specific states with private virtual name space – Intercepts system calls to expose only virtual identifiers (e.g., vpid) – Preserves resource names and dependencies across migration • Mechanism to checkpoint and restart states – User and kernel-level state – Primarily uses system call handlers – File system not saved or restored
  • 12. DMTCP • Distributed Multi-Threaded CheckPointing. • Works with Linux Kernel 2.6.9 and later. • Supports sequential and multi-threaded computations across single/multiple hosts. • Entirely in user space (no kernel modules or root privilege). – Transparent (no recompiling, no re-linking). • Written in Northeastern University and MIT and under active development since 2006. • License: GNU LGPL (allows freely using and linking)
  • 13. Process Structure CT = DMTCP checkpoint thread T = User Thread Coordinator Signal (USR2) DMTCP CT CT Process 1 Process N T1 T1 T2 Network Socket dmtcp_checkpoint <EXE> # starts coordinator dmtcp_command –c # talks to coordinator dmtcp_restart ckpt_<EXE>-*.dmtcp • Coordinator: a stateless synchronization server for the distributed checkpointing algorithm. • Checkpoint/Restart performance related to size of memory, disk write speed, and synchronization.
  • 14. How DMTCP works (1/4) • MTCP : component for checkpoint single-process • SIGUSR2: Used internally from checkpoint thread to user threads. Checkpoint thread CT 1. CT send SIGUSR2 to each threads for suspend T1 T2 2. Write checkpoint image to disk User program 3. Exit SIGUSR2 handler, and resume.
  • 15. How DMTCP works (2/4) • LD_PRELOAD: Transparently preloads checkpoint libraries `dmtcphijack.so` which installs libc wrappers and checkpointing code. • Wrappers: Only on less heavily used calls to libc – open, fork, exec, system, pipe, bind, listen, setsockopt, connect, accept, clone, close, ptsname, openlog, closelog, signal, sigaction, sigvec, sigblock, sigsetmask, sigprocmask, rt_sigprocmask, pthread_sigmask – Overhead is negligible. int open(const char *path, int open(const char *path, int flags){ int flags){ ... ... ... fd = open(path, funcs[_open](path, flags); } flags); ... } ... libc.so User Program dmtcphijack.so
  • 16. How DMTCP works (3/4) • Additional wrappers when process id & thread id virtualization is enabled – getpid, getppid, gettid, tcgetpgrp, tcsetprgrp, getgrp, setpgrp, getsid, setsid, kill, tkill, tgkill, wait, waitpid, waitid, wait3, wait4 int getpid(){ int getpid(){ ... ... ... } pid = getpid(); real_pid = funcs[_getpid](); ... return pid_table[real_pid]; } libc.so User Program dmtcphijack.so
  • 17. How DMTCP works (4/4) • Checkpoint image compression on-the-fly (default). • Currently only supports dynamically linking to libc.so. Support for static libc.a is feasible, but not implemented.
  • 18. Checkpoint under DMTCP(1/7) • dmtcphijack.so and libmtcp.so present in executable’s memory. – dmtcp_checkpoint <EXE> Coordinator Connect to exist coordinator or create a new coordinator CT CT T1 T2 T1 T2 User program User program
  • 19. Checkpoint under DMTCP(2/7) • Ask coordinator process for checkpoint via dmtcp_command. – dmtcp_command -c • DMTCP also provides API to send command or query status Coordinator Send checkpoint command CT CT command T1 T2 T1 T2 User program User program
  • 20. Checkpoint under DMTCP(3/7) • Suspend user threads with SIGUSR2. 1. send command for prepare checkpoint Coordinator CT CT 2. CT send SIGUSR2 to each threads for suspend T1 T2 T1 T2 User program User program
  • 21. Checkpoint under DMTCP(4/7) • Pre-checkpoint stage • Synchronize every node and elect shared file descriptor leaders. • Drain kernel buffers and do network handshake with peers. Wait until all node are ready. Coordinator 1. Report all thread except CT are suspended CT CT 2. Drain buffers T1 T2 T1 T2 User program User program
  • 22. Checkpoint under DMTCP(5/7) • Write checkpoint to disk – One checkpoint file per process – ckpt_<EXE>_<uid>.dmtcp Wait until all node checkpoint are done Coordinator CT CT Write checkpoint to disk seprately T1 T2 T1 T2 User program User program
  • 23. Checkpoint under DMTCP(6/7) • Post-Checkpint stage • Refill kernel buffers Wait until all node post-checkpoint are done Coordinator CT CT Refill buffer and re-handshake with peers. T1 T2 T1 T2 User program User program
  • 24. Checkpoint under DMTCP(7/7) • Resume user threads. Send resume command Coordinator CT CT Resume! T1 T2 T1 T2 User program User program
  • 25. Restart under DMTCP(1/6) • Restart Process loads in memory. – dmtcp_restart ckpt_<EXE>_<uid>.dmtcp Coordinator 1. Connect to exist coordinator or create a new coordinator CT 2. Load process to memroy dmtcp_restart
  • 26. Restart under DMTCP(2/6) • Fork user program Coordinator CT CT dmtcp_restart dmtcp_restart
  • 27. Restart under DMTCP(3/6) • Reopen files and recreate ptys • Recreate and reconnect sockets • Rearrange file descriptors to initial layout Coordinator Wail all node recreate socket and reopen file 1. Reopen file/ptys/sockets CT CT 2. Rearrange FD via dup2 dmtcp_restart dmtcp_restart
  • 28. Restart under DMTCP(4/6) • Restore memory content. • Restore stack status for checkpoint thread. FDs will preserved across execve! dmtcp_restart execve Coordinator mtcp_restart Coordinator mmap + magic!! User program CT CT CT CT dmtcp_restart dmtcp_restart User program User program
  • 29. Restart under DMTCP(5/6) • Restore other threads. – Recreate thread and restore stack and context. – Restore back to the post-checkpint stage • Refill kernel buffer Coordinator Wail all node restore done 1. Memory and thread come back now! CT CT T1 T2 T1 T2 2. Refill buffers User program User program
  • 30. Restart under DMTCP(6/6) • Resume user threads stopthisthread <sig-handler> ... <user_funcN> while (mtcp_state_value(&thread -> state) ... == ST_SUSPENDED) { mtcp_state_futex (&(thread -> state), <user_func2> FUTEX_WAIT, ST_SUSPENDED, Coordinator <user_func1> NULL); } Thread Call Stack ... CT CT Resume! T1 T2 T1 T2 User program User program
  • 31. DMTCP Workflow Start with dmtcp Restart wrapper Re-open FDs Run Get checkpoint command Restore memory Pre-Checkpoint Restore threads Checkpoint Provide hook point! Post-Checkpoint
  • 32. OS Features supported by DMTCP • Threads, mutexes/semaphores, fork, exec • Shared memory (via mmap), TCP/IP sockets, UNIX domain sockets, pipes, ptys, terminal modes, ownership of controlling terminals, signal handlers, open and/or shared fds, I/O (including the readline library), parent-child process relationships, process id & thread id virtualization, session and process group ids, and more…
  • 33. DMTCP/Android: Additional Features (LGPL; separated from Android) • ARM Architecture support – Verified on Samsung Galaxy S2 + Android 4.0 • Binder IPC – Client: supported – Server: partially supported • Ashmem: supported • Logger: supported • Properties: supported • Wakelocks: Not supported Source code is available https://github.com/0xlab/dmtcp-android https://github.com/0xlab/android-checkpoint
  • 34. Support new FD type in DMTCP • In DMTCP, every FD has an associated `Connection`: – TcpConnection, FileConnection, PtyConnection • Implement a new subclass of Connection if you want to support a new FD type for Android: ● AshmemConnection, BinderConnection, LoggerConnection, PropertyConnection • Also, implement the preCheckpoint, postCheckpint, and any others if needed.
  • 35. Interface of Connection class Connection { public: virtual void preCheckpoint (const dmtcp::vector<int>&, KernelBufferDrainer&); virtual void postCheckpoint (const dmtcp::vector<int>&, bool); virtual void restore (const dmtcp::vector<int>&, ConnectionRewirer *); virtual bool isDupConnection (const Connection&, dmtcp::ConnectionToFds&); virtual void doLocking (const dmtcp::vector<int>&); virtual void saveOptions (const dmtcp::vector<int>&); virtual void restoreOptions (const dmtcp::vector<int>& ); virtual void doSendHandshakes (const dmtcp::vector<int>&, const dmtcp::UniquePid&); virtual void doRecvHandshakes (const dmtcp::vector<int>&, const dmtcp::UniquePid&); virtual void restartDup2 (int, int); protected: virtual void serializeSubClass (jalib::JBinarySerializer&); };
  • 36. Android Binder support for DMTCP • BinderConnection – Reopen /dev/binder and reset ioctl parameters – Restore the mmap region • Hijack the whole libbinder – Prevent libbinder from interpreting data twice – Implement necessary DMTCP hooks: preCheckpoint, postCheckpoint, postRestart • Re-initialize libbinder in postRestart • The server part is partially supported because binder server is calling a blocked ioctl and blocking the whole checkpoint process. – We implement an early checkpoint stage to suspend such kind of threads.
  • 37. More extensions in DMTCP/Android • Improve the hook system in DMTCP – Original design only allows one set hook function. – Allow more than one set hook function in DMTCP/Android. • Implement per thread callback hook – Restore the DVM internal thread info • Add barrier and synchronize mechanisms to DMTCP – In order to make precise program checkpointing.
  • 38. Android specific modifications • Reorder code in framework – registerZygoteSocket() • The socket is inherited from the parent process `init`, which implies we can not handle it in DMTCP. – Move few initializations later than the checkpoint process since the current binder support is incomplete. • Reserve the ashmem's file descriptor – Original behavior is to close the fd after mmap – DMTCP binds connection to one fd, so the connection will be destroyed if that fd is closed. • Implement the missing PThread function in bionic libc – pthread_tryjoin_np is required by DMTCP, but it s not implemented in original bionic.
  • 39. Technical Issues when modifying • ARM Architecture support is incomplete. DMTCP – We are going to contribute back to upstream. • Different TLS implementation semantics between glibc and bionic libc – DMTCP/Android follows the techniques used in Android´s OpenGL ES package which links and defers to the slot of TLS in bionic libc. Not elegant, but it works • PThread implementation expectation is quite different – AOSP master branch is merging libc from NetBSD, so it should be better for compatibility. • Behavior of dynamic linker differs a lot in bionic libc. • Flags in dlopen() is not really functional. • The way to find symbol in bionic libc differs: weak symbol
  • 40. Checkpoint for Zygote • Experiment environment: – Android-x86 ICS emulated by VirtualBox – Host: Thinkpad x200 (Intel Core 2 Due @ 2.4 GHz) with gzip without gzip ~10s ~5.5s Checkpoint time ~0.5s ~0.2s Restart time ~3M ~17M Image size
  • 41. Observations from logcat --------- beginning of /dev/log/system --------- beginning of /dev/log/system I/Vold ( 1270): Vold 2.1 (the revenge) firing up I/Vold ( 1270): Vold 2.1 (the revenge) firing up D/Vold ( 1270): Volume usb state changing -1 (Initializing) -> 0 (No-Media) D/Vold ( 1270): Volume usb state changing -1 (Initializing) -> 0 (No-Media) I/Netd ( 1271): Netd 1.0 starting I/Netd ( 1271): Netd 1.0 starting I/ ( 1275): ServiceManager: 0x8062b50 I/ ( 1275): ServiceManager: 0x8062b50 I/ ( 1276): ServiceManager: 0x804fb98 I/ ( 1276): ServiceManager: 0x804fb98 I/AudioFlinger( 1276): Loaded primary audio interface from LEGACY Audio HW I/AudioFlinger( 1276): Loaded primary audio interface from LEGACY Audio HW HAL (audio) I/AudioFlinger( 1276): Using 'LEGACY Audio HW HAL' (audio.primary) as I/AudioFlinger( 1276): Using 'LEGACY Audio HW HAL' (audio.primary) as the the primary audio interface ... …. D/AudioHardware( 1276): ### setVoiceVolume: 1.000000 D/AudioHardware( 1276): ### setVoiceVolume: 1.000000 I/AudioPolicyService( 1276): [1276]Loaded audio policy from LEGACY Audio P I/AudioPolicyService( 1276): [1276]Loaded audio policy from LEGACY Audio Policy HAL (audio_policy) E/BatteryService( 1382): usbOnlinePath not found D/dalvikvm( 1373): GC_EXPLICIT freed 14K, 1% free 6418K/6467K, paused 0 D/AndroidRuntime( 1902): D/dalvikvm( 1373): GC_EXPLICIT freed 5K, 1% free 6412K/6467K, paused 0m D/dalvikvm( 1373): GC_EXPLICIT freed <1K, 1% free 6412K/6467K, paused 0 D/AndroidRuntime( 1902): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<< D/AndroidRuntime( 1902): CheckJNI is ON I/dalvikvm( 1373): System server process 1382 has been created I/SamplingProfilerIntegration( 1902): Profiling disabled. I/Zygote ( 1902): Preloading classes... D/dalvikvm( 1902): GC_EXPLICIT freed 35K, 85% free 399K/2560K, paused 0ms+0ms ... I/Zygote ( 1902): ...preloaded 379 resources in 548ms. D/dalvikvm( 1902): GC_EXPLICIT freed 20K, 1% free 6417K/6467K, paused 0ms+0ms I/Zygote ( 1902): ...preloaded 31 resources in 13ms. D/dalvikvm( 1902): GC_EXPLICIT freed 14K, 1% free 6418K/6467K, paused 0ms+0ms D/dalvikvm( 1902): GC_EXPLICIT freed 5K, 1% free 6412K/6467K, paused 0ms+0ms D/dalvikvm( 1902): GC_EXPLICIT freed <1K, 1% free 6412K/6467K, paused 0ms+2ms I/dalvikvm( 1902): System server process 1911 has been created Normal bootup log message Bootup log message with restart
  • 42. Android Boottime with DMTCP 1 2 3 4 5 6 7 8 9 10 avg 27.96 27.95 32.89 26.59 32.33 32.36 33.22 32.99 36.47 32.85 31.56 Boottime Boottime 15.02 15.86 15.13 14.88 14.57 14.43 14.73 14.22 13.97 14.61 14.74 with DMTCP (w/ gzip) Boottime 14.98 15.13 14.61 13.90 14.72 14.84 15.46 15.06 15.32 15.39 14.94 with DMTCP (w/o gzip) Measured by uptime in onStart() of Launcher2
  • 43. Reversible Debugger based on DMTCP • URDB is a universal reversible debugger that can add reversibility gained through the use of DMTCP. • A user debugging with gdb would then ask URDB to go back to a point in time to when: – the expression had a correct value – the next statement would cause the expression to take on an incorrect value. • Project page: http://sourceforge.net/projects/urdb/
  • 44. Reversible Debugger using Checkpointing
  • 45. Reference • “DMTCP: An New Linux Checkpointing Mechanism for Vanilla Universe Job”, Condor Project, University of Wisconsin-Madison • “Checkpointing using DMTCP, Condor, Matlab and FReD”, Gene Cooperman, Northeastern University, Boston • URDB: Universal Reversible Debugger http://arxiv.org/abs/0910.5046 • Cruz: Application-Transparent Distributed Checkpoint-Restart on Standard Operating Systems, G. (John) Janakiraman, Jose Renato Santos, Dinesh Subhraveti, Yoshio Turner, HP Labs