Reboots are for hardware: challenges and solutions to updating an operating system on the fly Baumann, Andrew en_US Appavoo, Jonathan en_US Wisniewski, Robert en_US Da Silva, Dilma en_US Krieger, Orran en_US Heiser, Gernot en_US 2021-11-25T13:32:15Z 2021-11-25T13:32:15Z 2007 en_US
dc.description.abstract Patches to modern operating systems, including bug fixes and security updates, and the reboots and downtime they require, cause tremendous problems for system users and administrators. Dynamic update allows an operating system to be patched without the need for a reboot or other service interruption. We have taken the approach of building dynamic update functionality directly into an existing operating system, K42. To determine the applicability of our update system, and to investigate the changes that are made to OS code, we analysed K42’s revision history. The analysis showed that our original system could only support half of the desired changes to K42. The main problem preventing more changes from being converted to dynamic updates was our system’s inability to update interfaces. Other studies, as well as our own investigations, have shown that change to interfaces is also prevalent in systems such as Linux. Thus, it is apparent that a dynamic update mechanism needs to handle interface changes to be widely applicable. In this paper, we describe how to support interface changes in a modular dynamic update system. With this improvement, approximately 79% of past performance and bug fix changes to K42 could be converted to dynamic updates, and we expect the proportion would be even higher if the fixes were being developed for dynamic update. Measurements of our system show that the runtime overhead is very low, and the time to apply updates is acceptable. This paper makes the following contributions. We present a mechanism to handle interface changes for dynamic updates to an operating system. For performance sensitive updates, we show how to apply changes lazily. We discuss lessons learned, including how an operating system can be structured to better support dynamic update. We also describe how our approach extends to other systems such as Linux, that although structured modularly, are not strictly object-oriented like K42. en_US
dc.description.uri en_US
dc.identifier.isbn 1931971536 en_US
dc.language English
dc.language.iso EN en_US
dc.publisher USENIX association en_US
dc.rights CC BY-NC-ND 3.0 en_US
dc.rights.uri en_US
dc.source Legacy MARC en_US
dc.title Reboots are for hardware: challenges and solutions to updating an operating system on the fly en_US
dc.type Conference Paper en
dcterms.accessRights open access
dspace.entity.type Publication en_US
unsw.description.publisherStatement Original publication by the USENIX Association. en_US
unsw.identifier.doi CA, USA en_US
unsw.relation.faculty Engineering
unsw.relation.ispartofconferenceLocation Santa Clara,USA en_US
unsw.relation.ispartofconferenceName 2007 USENIX annual technical conference en_US
unsw.relation.ispartofconferenceProceedingsTitle 2007 USENIX annual technical conference, Proceedings en_US
unsw.relation.ispartofconferenceYear 2007 en_US
unsw.relation.ispartofpagefrompageto 337-350 en_US
unsw.relation.originalPublicationAffiliation Baumann, Andrew, Computer Science & Engineering, Faculty of Engineering, UNSW en_US
unsw.relation.originalPublicationAffiliation Appavoo, Jonathan en_US
unsw.relation.originalPublicationAffiliation Wisniewski, Robert en_US
unsw.relation.originalPublicationAffiliation Da Silva, Dilma en_US
unsw.relation.originalPublicationAffiliation Krieger, Orran en_US
unsw.relation.originalPublicationAffiliation Heiser, Gernot, Computer Science & Engineering, Faculty of Engineering, UNSW en_US School of Computer Science and Engineering *
Original bundle
Now showing 1 - 1 of 1
Thumbnail Image
149.12 KB
Resource type