Changes between Version 5 and Version 9 of Ticket #414
- Timestamp:
- 2013-03-28T17:54:36Z (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #414
- Property Keywords gsoc13 added
- Property Component helenos/kernel/generic → helenos-infrastructure
-
Ticket #414 – Description
v5 v9 1 1 Design and implement graceful shutdown of HelenOS. 2 2 3 4 3 Details:: 5 The current support for shutdown in HelenOS is rather minimal. 6 It is possible to halt the CPUs or reboot the machine. 7 What is missing is a ''graceful'' way to tell running tasks that the system is about to be shut down. 8 For example, the reboot sequence now consists of forceful kill of all existing tasks.[[br]] 9 The goal is to design and implement way to notify tasks of imminent shutdown (reboot) to allow them terminate in a clean and consistent way. 10 The design decisions must reflect microkernel-specific issues, such as order of shutdown of vital services (e. g. VFS, naming service or drivers). 11 4 The current support for shutdown in HelenOS is rather minimal. It is possible to halt the CPUs or reboot the machine. What is missing is a ''graceful'' way to tell running tasks that the system is about to be shut down. For example, the reboot sequence now consists of forceful kill of all existing tasks. The goal is to design and implement way to notify tasks of imminent shutdown (reboot) to allow them terminate in a clean and consistent way. The design decisions must reflect microkernel-specific issues, such as order of shutdown of vital services (e. g. VFS, naming service or drivers). 12 5 13 6 What Gains and Benefits will this bring?:: 14 The benefits of this task come at rather low level but are nevertheless very important. 15 Graceful shutdown means that drivers could terminate communication with hardware in a predictable manner or that filesystem servers would be able to unmount file systems cleanly. 7 The benefits of this task come at rather low level but are nevertheless very important. Graceful shutdown means that drivers could terminate communication with hardware in a predictable manner or that filesystem servers would be able to unmount file systems cleanly. 16 8 17 9 18 10 Difficulty:: 19 Medium to difficult. The solution will require work both in kernel and in userspace. 20 11 Medium to High. The solution will require work both in kernel and in userspace. 21 12 22 13 Required skills:: 23 A successful applicant will have good skills of programming in the C languages and the ability to survive in a non-standard non-POSIX application environment. 24 14 A successful applicant will have good skills of programming in the C languages and the ability to survive in a non-standard non-POSIX application environment. 25 15 26 16 Documentation:: … … 30 20 31 21 Possible mentors:: 32 HelenOS Core Team, Vojtech Horky22 HelenOS Core Team, Vojtech Horky