DOCSLIB.ORG

Improving Linux Startup Time Using Software Resume (And Other Techniques)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Improving Linux Startup Time Using Software Resume (And Other Techniques) Improving Linux Startup Time Using Software Resume (and other techniques) Hiroki Kaminaga Sony Corporation [email protected] Abstract 1 Software suspend This paper presents a new resume operation as Snapshot boot is based on the current software well as other startup time improvement tech- suspend technology in the Linux kernel. Soft- niques which are aimed at achieving fast startup ware suspend is independent of APM or ACPI, time for embedded Linux systems. A new which makes it more applicable to embedded fast boot method called snapshot boot is intro- systems, where APM or ACPI is not present in duced. Snapshot boot is essentially a resume- many cases. Before describing snapshot boot, from-disk operation, which is a system resume the standard procedure of software suspend is from a semi-permanent snapshot image stored described to assist in understanding the proce- on disk or flash memory, that restores the ma- dure of snapshot boot. chine to a known running state. As opposed to a standard resume operation, a snapshot im- age is made only once, stored on disk or flash memory, and same image is used repeatedly, 1.1 Suspend states in Linux kernel every time the system is powered on. Other fast boot techniques that are discussed are: use of prelinking, a scheme to reduce the startup There are three suspend states in the Linux ker- cost of symbol relocation overhead for links to nel [1]. They are: dynamic libraries, execute in place (XIP) to re- duce or avoid OS and application loading de- lays, toolchain modifications to collect global • Standby state constructors in one place to accomplish a lo- cality benefit, and making the program .data • Suspend-to-RAM state section demand-paged from flash to avoid fully loading its pages on startup. • Suspend-to-disk state Unless otherwise stated, the startup time re- ferred to in this paper is the time from the sys- tem power on to the time user can manipulate Unless otherwise stated, the term suspend is the device. This includes userland application referred to as Suspend-to-disk. This is also startup as well as kernel startup time. known as hibernation. 18 • Improving Linux Startup Time Using Software Resume (and other techniques) 1.2 Suspend procedure 6. Save processor state This is done by calling the save_ processor_state() procedure. It will The suspend procedure is shown below: save registers other than generic ones, such as segment registers, co-processor registers, and so on. 1. Trigger Suspend procedure is triggered from writ- 7. Save processor registers ing disk to /sys/power/state opera- This is done by calling the swsusp_ tion. The call stack to the entrance of the arch_suspend() procedure. It will save suspend procedure is shown in Figure 1. general registers. This is written in assem- bly language, since the stack may not be sys_write() used. +-vfs_write() +-sysfs_write_file() 8. Allocate memory for snapshot image +-flush_write_buffer() This is done by calling the swsusp_ +-subsys_attr_store() +-state_store() alloc() procedure. Page directories +-enter_state() get allocated by calling __get_free_ +-pm_suspend_disk() pages(), and pages for the image itself gets allocated by get_zeroes_page() Figure 1: Call graph to entrance of software for each page directory entry. suspend 9. Copy memory contents to allocated area This is done by calling the copy_data_ 2. Freeze processes pages() procedure. It calls memcpy() This is done by calling the freeze_ for each page to copy. processes() procedure. It freezes user processes, and then freezes kernel tasks. 10. Restore processor state This is done by calling the 3. Free unnecessary memory restore_processor_state() pro- This is done by calling the free_some_ cedure in swsusp_suspend(). This memory() procedure. It calls shrink_ is where the software suspend resume all_memory() inside. procedure comes back. It restores the previously saved processor state. 4. Suspend devices This is done by calling the device_ 11. Power up devices suspend() procedure. It calls suspend_ This is done by calling the device_ device() and then the suspend() power_up() procedure. It resumes sys- method for all listed active devices. tem devices and all listed power off de- vice. 5. Power down devices This is done by calling the device_ 12. Resume devices power_down() procedure. It calls This is done by calling the device_ suspend_device() to for all listed resume() procedure. It resumes devices power off devices. in power off device list. 2006 Linux Symposium, Volume Two • 19 13. Write page, pagedir, header image to swap 5. Read page directory into allocated mem- Now that the devices are active, write ory to swap could be performed. This is This is done by calling the read_ done by calling the write_suspend_ pagedir() procedure. It allocates page image() procedure. It writes image data, directory memory space by using __get_ page directories, and then image header free_pages() and reads page directory into swap. information with bio_read_page(). 14. Power down devices 6. Relocate page directory (if necessary) This is done by calling the device_ shutdown() procedure. It calls the shut- 7. Read swap image into allocated memory down() method for each device. Then, the This is done by calling the data_read() system device is shutdown. procedure. The page directory area gets relocated if it collides with the snapshot 15. Halt machine image. Then the snapshot image is read This is done by calling the machine_ from swap with bio_read_page(). power_off() procedure. It calls pm_ power_off() and the machine halts. 8. Prepare resume 9. Freeze process 1.3 Resume procedure 10. Free unnecessary memory 11. Suspend devices The resume procedure is shown below: These steps are taken to accomplish con- sistency between suspend and resume, and in case resume fails. These steps are same Start resume 1. as Steps 2 to 4 of the suspend procedure. Resume starts by calling the software_resume() procedure in 12. Power down devices do_initcalls(), at late_initcall This step is taken to accomplish consis- timing. tency between suspend and resume. This step is same as Step 5 of the suspend pro- 2. Check kernel parameter cedure. In software_resume(), it checks for the kernel command line for the resume 13. Save processor state swap device. These steps are taken in case resume fails. These steps are same as Step 6 of the sus- 3. Check signature and header of snapshot pend procedure. image This is done by calling the check_sig() 14. Copy snapshot image in allocated memory and check_header() procedures. It to its original address checks swap image signature for snapshot image, and that the header for the kernel 15. Restore processor registers used for suspend and resume is the same. This is done by calling the swsusp_ arch_resume() procedure. It copies all 4. Allocate memory space for snapshot im- image pages from the allocated memory age address to its original memory address. 20 • Improving Linux Startup Time Using Software Resume (and other techniques) It also restores general purpose registers. Kit (OSK5912) reference board was used [4]. Since registers are restored, the return ad- Since this board does not have a disk, NOR dress used by this function would be the flash is used to store the snapshot image. same as the one in effect for the swsusp_ arch_suspend() procedure call at sus- To enable software suspend, the CONFIG_PM pend time. and CONFIG_SOFTWARE_SUSPEND configura- tion options must be set when building the linux 16. Restore processor state kernel. After the target is booted with the new kernel, the following commands were issued to 17. Power up devices enter suspend. This is exactly the same as Steps 10 to 11 of the suspend procedure. # mkswap /dev/mtdblock3 18. Free memory allocated for image # swapon /dev/mtdblock3 This is done by calling the free_image_ # mount -t sysfs none /sys pages() procedure. It does free_ # echo disk >/sys/power/state page() for all pages in image. Page di- rectories are also freed. A kernel message is printed to console, and the 19. Resume devices system would halt. At the next system power resume=/dev/ This is done by calling the device_ on, passing the argument: mtdblock3 resume() procedure. The process is the (in the above case) will trigger same as Step 12 of the suspend procedure. software resume. 20. Thaw processes This is done by calling the thaw_ 2 Snapshot boot processes() procedure. This wakes up every thread by calling the wake_up_ process() procedure. 2.1 Preserving snapshot image 1.4 Software suspend support for ARM ar- For normal use of software suspend and re- chitecture sume, a snapshot image is created and de- stroyed on every suspend/resume cycle. Since the aim of using software suspend in an embed- Software suspend does not support the ARM ded product in this paper is to improve startup architecture in a vanilla kernel. To port soft- time, a snapshot image is created only once, ware suspend for other architectures, a porting stored on disk or flash memory, and the same note [2] was followed which shows how to port image is used repeatedly, every time the system for the ARM architecture. The patch for soft- is powered on. This is accomplished by not in- ware suspend ARM support is posted to a pub- validating the snapshot image at resume time. lic mailing list [3]. 2.2 Principle of software resume for im- 1.5 Execution of software suspend proving startup time To evaluate software suspend for an embedded The time to a certain point in running system system, an ARM-based OMAP 5912 Starter state could be roughly expressed as follows: 2006 Linux Symposium, Volume Two • 21 startup time = ∑Storage to RAM + • The snapshot image is copied twice. ∑setup I/O state + ∑setup RAM state • There is redundancy in device state transi- tions during booting.
Load more

Recommended publications
  • Shorten Device Boot Time for Automotive IVI and Navigation Systems
    Shorten Device Boot Time for Automotive IVI and Navigation Systems Jim Huang ( 黃敬群 ) <[email protected]> Dr. Shi-wu Lo <[email protected]> May 28, 2013 / Automotive Linux Summit (Spring) Rights to copy © Copyright 2013 0xlab http://0xlab.org/ [email protected] 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: May 28, 2013 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 Goal of This Presentation • Propose a practical approach of the mixture of ARM hibernation (suspend to disk) and Linux user-space checkpointing – to shorten device boot time • An intrusive technique for Android/Linux – minimal init script and root file system changes are required • Boot time is one of the key factors for Automotive IVI – mentioned by “Linux Powered Clusters” and “Silver Bullet of Virtualization (Pitfalls, Challenges and Concerns) Continued” at ALS 2013 – highlighted by “Boot Time Optimizations” at ALS 2012 About this presentation • joint development efforts of the following entities – 0xlab team - http://0xlab.org/ – OSLab, National Chung Cheng University of Taiwan, led by Dr.
    [Show full text]
  • Proceedings of the Linux Symposium Volume
    Proceedings of the Linux Symposium Volume Two July 19th–22nd, 2006 Ottawa, Ontario Canada Contents Evolution in Kernel Debugging using Hardware Virtualization With Xen 1 Nitin A. Kamble Improving Linux Startup Time Using Software Resume (and other techniques) 17 Hiroki Kaminaga Automated Regression Hunting 27 A. Bowen, P. Fox, J. Kenefick, A. Romney, J. Ruesch, J. Wilde, & J. Wilson Hacking the Linux Automounter—Current Limitations and Future Directions 37 Ian Maxwell Kent & Jeff Moyer Why NFS Sucks 51 Olaf Kirch Efficient Use of the Page Cache with 64 KB Pages 65 Dave Kleikamp and Badari Pulavarty Startup Time in the 21st Century: Filesystem Hacks and Assorted Tweaks 71 Benjamin C.R. LaHaise Using Hugetlbfs for Mapping Application Text Regions 75 H.J. Lu, K. Doshi, R. Seth, & J. Tran Towards a Better SCM: Revlog and Mercurial 83 Matt Mackall Roadmap to a GL-based composited desktop for Linux 91 K.E. Martin and K. Packard Probing the Guts of Kprobes 101 A. Mavinakayanahalli, P. Panchamukhi, J. Keniston, A. Keshavamurthy, & M. Hiramatsu Shared Page Tables Redux 117 Dave McCracken Extending RCU for Realtime and Embedded Workloads 123 Paul E. McKenney OSTRA: Experiments With on-the-fly Source Patching 139 Arnaldo Carvalho de Melo Design and Implementation to Support Multiple Key Exchange Protocols for IPsec 143 K. Miyazawa, S. Sakane, K. Kamada, M. Kanda, & A. Fukumoto The State of Linux Power Management 2006 151 Patrick Mochel I/O Workload Fingerprinting in the Genetic-Library 165 Jake Moilanen X86-64 XenLinux: Architecture, Implementation, and Optimizations 173 Jun Nakajima, Asit Mallick GCC—An Architectural Overview, Current Status, and Future Directions 185 Diego Novillo Shared-Subtree Concept, Implementation, and Applications in Linux 201 Al Viro & Ram Pai The Ondemand Governor 215 Venkatesh Pallipadi & Alexey Starikovskiy Linux Bootup Time Reduction for Digital Still Camera 231 Chan-Ju Park A Lockless Pagecache in Linux—Introduction, Progress, Performance 241 Nick Piggin The Ongoing Evolution of Xen 255 I.
    [Show full text]
  • Making Applications Mobile Under Linux
    Making Applications Mobile Under Linux Cédric Le Goater, Daniel Lezcano, Clément Calmels IBM France {clg, dlezcano, clement.calmels}@fr.ibm.com Dave Hansen, Serge E. Hallyn Hubertus Franke IBM Linux Technology Center IBM T.J. Watson Research Center {haveblue, serue}@us.ibm.com [email protected] Abstract a failure, a system upgrade, or a need to rede- ploy hardware resources. This ability to check- point context is most common in what is re- Application mobility has been an operating sys- ferred to as the High Performance Computing tem research topic for many years. Many (HPC) environment, which is often composed approaches have been tried and solutions are of large numbers of computers working on a found across the industry. However, perfor- distributed, long running computation. The ap- mance remains the main issue and all the ef- plications often run for days or weeks at a time, forts are now focused on performant solutions. some even as long as a year. In this paper, we will discuss a prototype which minimizes the overhead at runtime and the Even outside the HPC arena, there are many amount of application state. We will examine applications which have long start up times, constraints and requirements to enhance perfor- long periods of processing configuration files, mance. Finally, we will discuss features and en- pre-computing information and so on. Histor- hancements in the Linux kernel needed to im- ically, emacs was built with a script which in- plement migration of applications. cluded undump—the ability to checkpoint the full state of emacs into a binary which could then be started much more quickly.
    [Show full text]
  • Linux Kernel User Documentation V4.20.0
    usepackagefontspec setsansfontDejaVu Sans setromanfontDejaVu Serif setmonofontDejaVu Sans Mono Linux Kernel User Documentation v4.20.0 The kernel development community 1 16, 2019 Contents 1 Linux kernel release 4.x <http://kernel.org/> 3 2 The kernel’s command-line parameters 9 3 Linux allocated devices (4.x+ version) 109 4 L1TF - L1 Terminal Fault 171 5 Reporting bugs 181 6 Security bugs 185 7 Bug hunting 187 8 Bisecting a bug 193 9 Tainted kernels 195 10 Ramoops oops/panic logger 197 11 Dynamic debug 201 12 Explaining the dreaded “No init found.” boot hang message 207 13 Rules on how to access information in sysfs 209 14 Using the initial RAM disk (initrd) 213 15 Control Group v2 219 16 Linux Serial Console 245 17 Linux Braille Console 247 18 Parport 249 19 RAID arrays 253 20 Kernel module signing facility 263 21 Linux Magic System Request Key Hacks 267 i 22 Unicode support 273 23 Software cursor for VGA 277 24 Kernel Support for miscellaneous (your favourite) Binary Formats v1.1 279 25 Mono(tm) Binary Kernel Support for Linux 283 26 Java(tm) Binary Kernel Support for Linux v1.03 285 27 Reliability, Availability and Serviceability 293 28 A block layer cache (bcache) 309 29 ext4 General Information 319 30 Power Management 327 31 Thunderbolt 349 32 Linux Security Module Usage 353 33 Memory Management 369 ii Linux Kernel User Documentation, v4.20.0 The following is a collection of user-oriented documents that have been added to the kernel over time. There is, as yet, little overall order or organization here — this material was not written to be a single, coherent document! With luck things will improve quickly over time.
    [Show full text]
  • Optimization Techniques for Memory Virtualization-Based Resource Management
    SSStttooonnnyyy BBBrrrooooookkk UUUnnniiivvveeerrrsssiiitttyyy The official electronic file of this thesis or dissertation is maintained by the University Libraries on behalf of The Graduate School at Stony Brook University. ©©© AAAllllll RRRiiiggghhhtttsss RRReeessseeerrrvvveeeddd bbbyyy AAAuuuttthhhooorrr... Optimization Techniques for Memory Virtualization-based Resource Management A Dissertation Presented by Jui-Hao Chiang to The Graduate School in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Computer Science Stony Brook University December 2012 Stony Brook University The Graduate School Jui-Hao Chiang We, the dissertation committee for the above candidate for the Doctor of Philosophy degree, hereby recommend acceptance of this dissertation. Tzi-cker Chiueh { Dissertation Advisor Professor, Department of Computer Science Jie Gao { Chairperson of Defense Associate Professor, Department of Computer Science Rob Johnson Assistant Professor, Department of Computer Science Ted Teng Professor, Department of Technology and Society This dissertation is accepted by the Graduate School. Charles Taber Interim Dean of the Graduate School ii Abstract of the Dissertation Optimization Techniques for Memory Virtualization-based Resource Management by Jui-Hao Chiang Doctor of Philosophy in Computer Science Stony Brook University 2012 Memory virtualization abstracts the physical memory resources in a virtualized server in such a way that offers many resource man- agement advantages, such as consolidation, sharing,
    [Show full text]
  • Power Management on DICE Desktops Chris Cooke [email protected] What I’Ll Talk About
    Power Management on DICE desktops Chris Cooke [email protected] What I’ll talk about Power management What the project will deliver Main areas to look at Money Power management Basically - making computers use less electricity. Or, better - making them use it more efficiently. on PCs Formerly - APM Now - ACPI APM It was fairly simple. It worked (eventually). APM Control: APM was done at the BIOS level - the OS had little or no control. Hardware: the BIOS reckoned it knew exactly what hardware the machine had. APM worked ... ... but it wasn’t very flexible. ACPI The OS is in charge The ACPI spec defines multiple “states” - sleep states, CPU power states, etc. The OS asks the BIOS to do things ACPI Very flexible Lots more interaction between OS and BIOS Lots of chances for BIOS bugs to mess things up BIOS bugs According to Avery Pennarun: “BIOS programmers are crackheaded morons who can't implement an API correctly to save their lives.” http://www.advogato.org/person/apenwarr/ diary.html?start=167 ACPI It’s far more flexible than APM. It’s far more complicated than APM. It sometimes works ... ... sort of. ACPI on Linux It’s Open Source, so... Projects compete Projects fork and rename pm-utils, Powersave, swsusp, uswsusp, suspend, suspend2, TuxOnIce, gnome-power- manager, acpid, ... The project Just a report. Just looking at DICE desktops. Main Areas Could we make our DICE desktops... “sleep” at night? operate more efficiently when running? Sleeping at night What normally happens at night? Could it happen at other times? Or could we automatically wake up at night, perform maintenance (e.g.
    [Show full text]
  • Reducing the Boot Time of Embedded Linux Systems
    FACULTY OF INFORMATION TECHNOLOGY AND ELECTRICAL ENGINEERING Tomi Kyöstilä REDUCING THE BOOT TIME OF EMBEDDED LINUX SYSTEMS Master’s Thesis Degree Programme in Computer Science and Engineering September 2018 Kyöstilä T. (2018) Reducing the boot time of embedded Linux systems. University of Oulu, Degree Programme in Computer Science and Engineering. Master’s thesis, 51 p. ABSTRACT The increase of the functionality of consumer electronics has complicated the soft- ware embedded in them. The functionality previously implemented in hardware has been steadily shifting into software, which also increases its complexity. To- gether, these developments have led to reduced performance and longer start-up delays. Consumer electronics need to have a positive user experience, which is also affected by the boot time. The methods for reducing the start-up time of an embedded Linux system can be categorized by the boot phases they can target: bootloaders, kernel initial- ization, or user space initialization. Compression can be applied in various sit- uations, while prefetching to the page cache (readahead) is relevant only to user space initialization. Hibernation can be used to entirely avoid user space initial- ization, which is usually the most time-consuming boot phase in Android systems. Developers need to know what impact their solutions and hardware choices have on the boot time. For this purpose, a measurement system was developed, which can automatically reboot the target system and collect a large sample of start-up time measurements. A large sample size is important because of the variance of the boot time even in a fixed target configuration. The measurement system was validated by using it when optimizing the start- up time of an Android system for use in an embedded consumer electronics device.
    [Show full text]
  • Linux Kernel Power Management
    Linux Kernel Power Management Patrick Mochel Open Source Development Labs [email protected] Abstract cusses the mechanism for implementing hiber- nation, otherwise known as suspend-to-disk, support for Linux. Power management is the process by which the overall consumption of power by a com- puter is limited based on user requirements and 1 Overview policy. Power management has become a hot topic in the computer world in recent years, Benefits of Power Management as laptops have become more commonplace and users have become more conscious of the environmental and financial effects of limited A sane power management infrastructure pro- power resources. vides many benefits to the kernel, and not only in the obvious areas. While there is no such thing as perfect power management, since all computers must use Battery-powered devices, such as embedded some amount of power to run, there have been devices, handhelds, and laptops reap most of many advances in system and software archi- the rewards of power management, since the tectures to conserve the amount of power being more conservative the draw on the battery is, used. Exploiting these features is key to pro- the longer it will last. viding good system- and device-level power management. System power management decreases boot time of a system, by restoring previously saved This paper discusses recent advances in the state instead of reinitializing the entire system. power management infrastructure of the Linux This conserves battery life on mobile devices kernel that will allow Linux to fully exploit the by reducing the annoying wait for the computer power management capabilities of the various to boot into a useable state.
    [Show full text]
  • Cloning L4linux
    Diploma Thesis Cloning L4Linux Sebastian Sumpf March 27, 2007 Technische Universität Dresden Department of Computer Science Professor: Prof. Dr. rer. nat. Hermann Härtig Tutor: Dipl.-Inf. Norman Feske Statement Hereby I declare that this work was produced in an autonomous fashion and that I did use the specified resources only. Dresden, den March 27, 2007 Sebastian Sumpf Acknowledgments Thanks to Krause for her extraordinary patience and the rest of the “outside world”! Contents 1 Introduction 1 1.1 Virtualization classification . 1 1.2 Virtualization properties . 2 1.3 Comparison of isolation . 2 1.4 L4Linux .................................... 4 1.5 Idea . 4 2 State of the art 6 2.1 L3 – A persistent system . 6 2.2 L4 and persistence . 7 2.3 Nomadic operating system . 10 2.4 VMWare ESX Server . 11 2.5 The Denali isolation kernel . 13 3 Design 15 3.1 Checkpointing . 15 3.1.1 Checkpointing preliminaries . 15 3.1.2 The frozen strategy . 17 3.2 Memory-resource sharing . 17 3.2.1 Copy-on-write design . 17 3.3 Post checkpoint memory-resource sharing . 19 3.3.1 Partial hashing . 20 4 Implementation 24 4.1 L4Linux checkpointing – The details . 24 4.1.1 Saving the kernel state . 24 4.1.2 Memory handling . 26 4.2 Cloning L4Linux ............................... 27 4.3 The Freezer . 29 4.3.1 The hashing thread . 31 IV Contents 5 Evaluation 34 5.1 Cloning . 34 5.2 Isolation comparison . 35 5.3 Hash collisions . 36 6 Outlook 38 7 Summary 40 Glossary 41 Bibliography 42 V List of Figures 1.1 Memory sharing of L4Linux clones .
    [Show full text]
  • Openvz Forum
    Subject: [RFC][PATCH 1/5] Virtualization/containers: startup Posted by Kirill Korotaev on Fri, 03 Feb 2006 16:57:18 GMT View Forum Message <> Reply to Message This patch introduces some abstract container/VPS kernel structure and tiny amount of operations on it. Patches following this one will be used for virtualization of some resources based on this container infrastructure, including those VPIDs patches I sent before. What is important here is that: - each VPS has unique ID - each process in kernel can belong to one VPS only Kirill --- ./include/linux/vps_info.h.vps_info2006-02-03 16:38:33.000000000 +0300 +++ ./include/linux/vps_info.h2006-02-03 16:49:26.000000000 +0300 @@ -0,0 +1,41 @@ +#ifndef __LINUX_VPS_INFO_H_ +#define __LINUX_VPS_INFO_H_ + +#include <asm/types.h> +#include <asm/atomic.h> + +struct task_struct; + +struct vps_info { +u32 id; +struct task_struct *init_task; +atomic_t refcnt; +}; + +extern struct vps_info host_vps_info; +typedef struct vps_info *vps_t; + +static inline vps_t get_vps(vps_t vps) +{ +atomic_inc(&vps->refcnt); +return vps; +} + +static inline void put_vps(vps_t vps) +{ +atomic_dec(&vps->refcnt); +} + Page 1 of 64 ---- Generated from OpenVZ Forum +#include <linux/sched.h> +#include <asm/current.h> + +static inline vps_t set_current_vps(vps_t vps) +{ +vps_t ret; + +ret = current->owner_vps; +current->owner_vps = vps; +return ret; +} + +#endif --- ./include/linux/sched.h.vps_info2006-02-03 16:38:33.000000000 +0300 +++ ./include/linux/sched.h2006-02-03 16:43:42.000000000 +0300 @@ -687,6 +687,7 @@ struct audit_context;/* See audit.c */ struct mempolicy; +struct vps_info; struct task_struct { volatile long state;/* -1 unrunnable, 0 runnable, >0 stopped */ @@ -845,6 +846,7 @@ struct backing_dev_info *backing_dev_info; struct io_context *io_context; +struct vps_info *owner_vps; unsigned long ptrace_message; siginfo_t *last_siginfo; /* For ptrace use.
    [Show full text]
  • Swsusp and U-Boot
    Extending the swsusp Hibernation Framework to ARM Russell Dill 1 2 Introduction • Russ Dill of Texas Instruments • swsusp/hibernation on ARM – Overview – Challenges – Implementation – Remaining work – Debugging • swsusp restore from U-Boot • Code at: – https://github.com/russdill/linux/commits/arm-hibernation-am33xx – https://github.com/russdill/commits/hibernation ● eLinux.org page: http://elinux.org/ARM_Hibernation 3 Motivation • Hibernation provides zero power consumption sleep • Allows for snapshot boot • Shares requirements with self-refresh only sleep modes – RTC-Only+DDR self-refresh 4 swsusp • Mainline hibernation implementation since 2.6.0 – TuxOnIce (Suspend2) • Uses swap device to store image • Can be used with uswsusp to support additional features – Encryption – Limitless storage options – Graphical progress • Limited to snapshotting 1/2 of system RAM 5 swsusp 6 swsusp 7 OMAP PM • Clocks – Clock gating – Clock domains – Clock scaling • Power – Power domains ● Logic ● Retention – Voltage scaling • PRCM Controls these features 8 AM33xx PM Overview • MPU, PER, and GFX power domains can be turned off during suspend • Current OMAP PM core assumes WKUP domain will always have power 9 WKUP Context • Used for: – Power, reset, and clock management (PRCM) – Pin mux configuration – modules that wake up the processor from suspend • After hibernation, we need to restore this state 1 0 PRCM • Power domains – Represented by arch/arm/mach-omap2/powerdomain.c 1 1 PRCM • Reset state and module state – Represented by omap_hwmod, leverage it 1 2 PRCM • Clocks domains – Represented by arch/arm/mach-omap2/clockdomain.c 1 3 PRCM • Clocks – Leverage the clock tree by adding context save/restore callbacks 1 4 pinctrl • Controls how internal signals are routed to external pins • Contains memory map of register area, but no complete description of registers • AM335X errata complicates the situation, certain registers lose context when the PER domain powers during suspend • The pinctrl subsystem needs knowledge of which registers are available, and which domain they are in.
    [Show full text]
  • Linux Power Documentation
    Linux Power Documentation The kernel development community Jul 14, 2020 CONTENTS i ii CHAPTER ONE APM OR ACPI? If you have a relatively recent x86 mobile, desktop, or server system, odds are it supports either Advanced Power Management (APM) or Advanced Configura- tion and Power Interface (ACPI). ACPI is the newer of the two technologies and puts power management in the hands of the operating system, allowing for more intelligent power management than is possible with BIOS controlled APM. The best way to determine which, if either, your system supports is to build a kernel with both ACPI and APM enabled (as of 2.3.x ACPI is enabled by default). If a working ACPI implementation is found, the ACPI driver will override and disable APM, otherwise the APM driver will be used. No, sorry, you cannot have both ACPI and APM enabled and running at once. Some people with broken ACPI or broken APM implementations would like to use both to get a full set of working features, but you simply cannot mix and match the two. Only one power management interface can be in control of the machine at once. Think about it.. 1.1 User-space Daemons Both APM and ACPI rely on user-space daemons, apmd and acpid respectively, to be completely functional. Obtain both of these daemons from your Linux distribu- tion or from the Internet (see below) and be sure that they are started sometime in the system boot process. Go ahead and start both. If ACPI or APM is not available on your system the associated daemon will exit gracefully.
    [Show full text]