2005-10-12 17:07:38 +02:00
|
|
|
/* Reincarnation Server. This servers starts new system services and detects
|
|
|
|
* they are exiting. In case of errors, system services can be restarted.
|
|
|
|
* The RS server periodically checks the status of all registered services
|
|
|
|
* services to see whether they are still alive. The system services are
|
|
|
|
* expected to periodically send a heartbeat message.
|
|
|
|
*
|
2009-12-11 01:08:19 +01:00
|
|
|
* Changes:
|
|
|
|
* Nov 22, 2009: rewrite of boot process (Cristiano Giuffrida)
|
|
|
|
* Jul 22, 2005: Created (Jorrit N. Herder)
|
2005-10-12 17:07:38 +02:00
|
|
|
*/
|
2005-10-20 22:31:18 +02:00
|
|
|
#include "inc.h"
|
2007-04-23 16:43:25 +02:00
|
|
|
#include <fcntl.h>
|
2009-12-11 01:08:19 +01:00
|
|
|
#include <a.out.h>
|
|
|
|
#include <minix/crtso.h>
|
2005-10-12 17:07:38 +02:00
|
|
|
#include "../../kernel/const.h"
|
|
|
|
#include "../../kernel/type.h"
|
2009-12-11 01:08:19 +01:00
|
|
|
#include "../../kernel/proc.h"
|
|
|
|
#include "../pm/mproc.h"
|
|
|
|
#include "../pm/const.h"
|
2005-10-12 17:07:38 +02:00
|
|
|
|
|
|
|
/* Declare some local functions. */
|
2009-12-11 01:08:19 +01:00
|
|
|
FORWARD _PROTOTYPE(void exec_image_copy, ( int boot_proc_idx,
|
|
|
|
struct boot_image *ip, struct rproc *rp) );
|
|
|
|
FORWARD _PROTOTYPE(void boot_image_info_lookup, ( endpoint_t endpoint,
|
|
|
|
struct boot_image *image,
|
|
|
|
struct boot_image **ip, struct boot_image_priv **pp,
|
|
|
|
struct boot_image_sys **sp, struct boot_image_dev **dp) );
|
|
|
|
FORWARD _PROTOTYPE(void fill_call_mask, ( int *calls, int tot_nr_calls,
|
|
|
|
bitchunk_t *call_mask, int call_base) );
|
2005-10-12 17:07:38 +02:00
|
|
|
FORWARD _PROTOTYPE(void init_server, (void) );
|
2006-03-10 17:10:05 +01:00
|
|
|
FORWARD _PROTOTYPE(void sig_handler, (void) );
|
2005-10-12 17:07:38 +02:00
|
|
|
FORWARD _PROTOTYPE(void get_work, (message *m) );
|
2006-10-25 15:40:36 +02:00
|
|
|
FORWARD _PROTOTYPE(void reply, (int whom, message *m_out) );
|
2005-10-12 17:07:38 +02:00
|
|
|
|
2009-12-11 01:08:19 +01:00
|
|
|
/* The buffer where the boot image is copied during initialization. */
|
|
|
|
PRIVATE int boot_image_buffer_size;
|
|
|
|
PRIVATE char *boot_image_buffer;
|
2005-10-12 17:07:38 +02:00
|
|
|
|
2009-12-11 01:08:19 +01:00
|
|
|
/* Macro to identify a system service in the boot image. This rules out
|
|
|
|
* kernel tasks and the root system process (RS).
|
|
|
|
*/
|
|
|
|
#define isbootsrvprocn(n) (!iskerneln((n)) && !isrootsysn((n)))
|
|
|
|
|
|
|
|
/* Flag set when memory unmapping can be done. */
|
|
|
|
EXTERN int unmap_ok;
|
2007-02-16 16:50:30 +01:00
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
/* SEF functions and variables. */
|
|
|
|
FORWARD _PROTOTYPE( void sef_local_startup, (void) );
|
|
|
|
|
2005-10-12 17:07:38 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* main *
|
|
|
|
*===========================================================================*/
|
|
|
|
PUBLIC int main(void)
|
|
|
|
{
|
|
|
|
/* This is the main routine of this service. The main loop consists of
|
|
|
|
* three major activities: getting new work, processing the work, and
|
|
|
|
* sending the reply. The loop never terminates, unless a panic occurs.
|
|
|
|
*/
|
|
|
|
message m; /* request message */
|
endpoint-aware conversion of servers.
'who', indicating caller number in pm and fs and some other servers, has
been removed in favour of 'who_e' (endpoint) and 'who_p' (proc nr.).
In both PM and FS, isokendpt() convert endpoints to process slot
numbers, returning OK if it was a valid and consistent endpoint number.
okendpt() does the same but panic()s if it doesn't succeed. (In PM,
this is pm_isok..)
pm and fs keep their own records of process endpoints in their proc tables,
which are needed to make kernel calls about those processes.
message field names have changed.
fs drivers are endpoints.
fs now doesn't try to get out of driver deadlock, as the protocol isn't
supposed to let that happen any more. (A warning is printed if ELOCKED
is detected though.)
fproc[].fp_task (indicating which driver the process is suspended on)
became an int.
PM and FS now get endpoint numbers of initial boot processes from the
kernel. These happen to be the same as the old proc numbers, to let
user processes reach them with the old numbers, but FS and PM don't know
that. All new processes after INIT, even after the generation number
wraps around, get endpoint numbers with generation 1 and higher, so
the first instances of the boot processes are the only processes ever
to have endpoint numbers in the old proc number range.
More return code checks of sys_* functions have been added.
IS has become endpoint-aware. Ditched the 'text' and 'data' fields
in the kernel dump (which show locations, not sizes, so aren't terribly
useful) in favour of the endpoint number. Proc number is still visible.
Some other dumps (e.g. dmap, rs) show endpoint numbers now too which got
the formatting changed.
PM reading segments using rw_seg() has changed - it uses other fields
in the message now instead of encoding the segment and process number and
fd in the fd field. For that it uses _read_pm() and _write_pm() which to
_taskcall()s directly in pm/misc.c.
PM now sys_exit()s itself on panic(), instead of sys_abort().
RS also talks in endpoints instead of process numbers.
2006-03-03 11:20:58 +01:00
|
|
|
int call_nr, who_e,who_p; /* call number and caller */
|
2005-10-12 17:07:38 +02:00
|
|
|
int result; /* result to return */
|
|
|
|
sigset_t sigset; /* system signal set */
|
|
|
|
int s;
|
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
/* SEF local startup. */
|
|
|
|
sef_local_startup();
|
|
|
|
|
2005-10-12 17:07:38 +02:00
|
|
|
/* Initialize the server, then go to work. */
|
|
|
|
init_server();
|
|
|
|
|
|
|
|
/* Main loop - get work and do it, forever. */
|
|
|
|
while (TRUE) {
|
|
|
|
|
|
|
|
/* Wait for request message. */
|
|
|
|
get_work(&m);
|
endpoint-aware conversion of servers.
'who', indicating caller number in pm and fs and some other servers, has
been removed in favour of 'who_e' (endpoint) and 'who_p' (proc nr.).
In both PM and FS, isokendpt() convert endpoints to process slot
numbers, returning OK if it was a valid and consistent endpoint number.
okendpt() does the same but panic()s if it doesn't succeed. (In PM,
this is pm_isok..)
pm and fs keep their own records of process endpoints in their proc tables,
which are needed to make kernel calls about those processes.
message field names have changed.
fs drivers are endpoints.
fs now doesn't try to get out of driver deadlock, as the protocol isn't
supposed to let that happen any more. (A warning is printed if ELOCKED
is detected though.)
fproc[].fp_task (indicating which driver the process is suspended on)
became an int.
PM and FS now get endpoint numbers of initial boot processes from the
kernel. These happen to be the same as the old proc numbers, to let
user processes reach them with the old numbers, but FS and PM don't know
that. All new processes after INIT, even after the generation number
wraps around, get endpoint numbers with generation 1 and higher, so
the first instances of the boot processes are the only processes ever
to have endpoint numbers in the old proc number range.
More return code checks of sys_* functions have been added.
IS has become endpoint-aware. Ditched the 'text' and 'data' fields
in the kernel dump (which show locations, not sizes, so aren't terribly
useful) in favour of the endpoint number. Proc number is still visible.
Some other dumps (e.g. dmap, rs) show endpoint numbers now too which got
the formatting changed.
PM reading segments using rw_seg() has changed - it uses other fields
in the message now instead of encoding the segment and process number and
fd in the fd field. For that it uses _read_pm() and _write_pm() which to
_taskcall()s directly in pm/misc.c.
PM now sys_exit()s itself on panic(), instead of sys_abort().
RS also talks in endpoints instead of process numbers.
2006-03-03 11:20:58 +01:00
|
|
|
who_e = m.m_source;
|
|
|
|
who_p = _ENDPOINT_P(who_e);
|
|
|
|
if(who_p < -NR_TASKS || who_p >= NR_PROCS)
|
|
|
|
panic("RS","message from bogus source", who_e);
|
|
|
|
|
2005-10-12 17:07:38 +02:00
|
|
|
call_nr = m.m_type;
|
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
/* Now determine what to do. Four types of requests are expected:
|
2005-10-12 17:07:38 +02:00
|
|
|
* - Heartbeat messages (notifications from registered system services)
|
|
|
|
* - System notifications (POSIX signals or synchronous alarm)
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
* - Ready to update messages (reply messages from registered services)
|
2005-10-12 17:07:38 +02:00
|
|
|
* - User requests (control messages to manage system services)
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* Notification messages are control messages and do not need a reply.
|
|
|
|
* These include heartbeat messages and system notifications.
|
|
|
|
*/
|
2009-09-29 20:47:56 +02:00
|
|
|
if (is_notify(m.m_type)) {
|
|
|
|
switch (who_p) {
|
|
|
|
case CLOCK:
|
2009-12-17 02:53:26 +01:00
|
|
|
do_period(&m); /* check services status */
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
continue;
|
|
|
|
case PM_PROC_NR: /* signal or PM heartbeat */
|
|
|
|
sig_handler();
|
2005-10-12 17:07:38 +02:00
|
|
|
default: /* heartbeat notification */
|
2009-12-02 10:54:50 +01:00
|
|
|
if (rproc_ptr[who_p] != NULL) { /* mark heartbeat time */
|
endpoint-aware conversion of servers.
'who', indicating caller number in pm and fs and some other servers, has
been removed in favour of 'who_e' (endpoint) and 'who_p' (proc nr.).
In both PM and FS, isokendpt() convert endpoints to process slot
numbers, returning OK if it was a valid and consistent endpoint number.
okendpt() does the same but panic()s if it doesn't succeed. (In PM,
this is pm_isok..)
pm and fs keep their own records of process endpoints in their proc tables,
which are needed to make kernel calls about those processes.
message field names have changed.
fs drivers are endpoints.
fs now doesn't try to get out of driver deadlock, as the protocol isn't
supposed to let that happen any more. (A warning is printed if ELOCKED
is detected though.)
fproc[].fp_task (indicating which driver the process is suspended on)
became an int.
PM and FS now get endpoint numbers of initial boot processes from the
kernel. These happen to be the same as the old proc numbers, to let
user processes reach them with the old numbers, but FS and PM don't know
that. All new processes after INIT, even after the generation number
wraps around, get endpoint numbers with generation 1 and higher, so
the first instances of the boot processes are the only processes ever
to have endpoint numbers in the old proc number range.
More return code checks of sys_* functions have been added.
IS has become endpoint-aware. Ditched the 'text' and 'data' fields
in the kernel dump (which show locations, not sizes, so aren't terribly
useful) in favour of the endpoint number. Proc number is still visible.
Some other dumps (e.g. dmap, rs) show endpoint numbers now too which got
the formatting changed.
PM reading segments using rw_seg() has changed - it uses other fields
in the message now instead of encoding the segment and process number and
fd in the fd field. For that it uses _read_pm() and _write_pm() which to
_taskcall()s directly in pm/misc.c.
PM now sys_exit()s itself on panic(), instead of sys_abort().
RS also talks in endpoints instead of process numbers.
2006-03-03 11:20:58 +01:00
|
|
|
rproc_ptr[who_p]->r_alive_tm = m.NOTIFY_TIMESTAMP;
|
2009-12-02 10:54:50 +01:00
|
|
|
} else {
|
|
|
|
printf("Warning, RS got unexpected notify message from %d\n",
|
|
|
|
m.m_source);
|
|
|
|
}
|
2005-10-12 17:07:38 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
/* See if this is a ready to update message.
|
|
|
|
* If the message was expected, update the originating process
|
|
|
|
*/
|
|
|
|
else if(call_nr == RS_LU_PREPARE) {
|
|
|
|
result = do_upd_ready(&m);
|
|
|
|
|
|
|
|
/* Send reply only if something went wrong. */
|
|
|
|
if (result != OK) {
|
|
|
|
m.m_type = result;
|
|
|
|
reply(who_e, &m);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If this is neither a ready to update message nor a notification
|
|
|
|
* message, it is a normal request.
|
2005-10-12 17:07:38 +02:00
|
|
|
* Handle the request and send a reply to the caller.
|
|
|
|
*/
|
2008-02-21 17:20:22 +01:00
|
|
|
else {
|
2009-05-08 14:38:14 +02:00
|
|
|
if (call_nr != GETSYSINFO &&
|
|
|
|
(call_nr < RS_RQ_BASE || call_nr >= RS_RQ_BASE+0x100))
|
2008-02-21 17:20:22 +01:00
|
|
|
{
|
|
|
|
/* Ignore invalid requests. Do not try to reply. */
|
|
|
|
printf("RS: got invalid request %d from endpoint %d\n",
|
|
|
|
call_nr, m.m_source);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2009-12-02 10:54:50 +01:00
|
|
|
/* Handler functions are responsible for permission checking. */
|
2005-10-12 17:07:38 +02:00
|
|
|
switch(call_nr) {
|
2009-12-17 02:53:26 +01:00
|
|
|
case RS_UP: result = do_up(&m); break;
|
2005-10-21 15:28:26 +02:00
|
|
|
case RS_DOWN: result = do_down(&m); break;
|
|
|
|
case RS_REFRESH: result = do_refresh(&m); break;
|
2006-10-20 17:01:32 +02:00
|
|
|
case RS_RESTART: result = do_restart(&m); break;
|
2005-10-21 15:28:26 +02:00
|
|
|
case RS_SHUTDOWN: result = do_shutdown(&m); break;
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
case RS_UPDATE: result = do_update(&m); break;
|
2005-10-21 15:28:26 +02:00
|
|
|
case GETSYSINFO: result = do_getsysinfo(&m); break;
|
2009-09-21 17:25:15 +02:00
|
|
|
case RS_LOOKUP: result = do_lookup(&m); break;
|
2005-10-12 17:07:38 +02:00
|
|
|
default:
|
|
|
|
printf("Warning, RS got unexpected request %d from %d\n",
|
|
|
|
m.m_type, m.m_source);
|
|
|
|
result = EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Finally send reply message, unless disabled. */
|
|
|
|
if (result != EDONTREPLY) {
|
2006-10-25 15:40:36 +02:00
|
|
|
m.m_type = result;
|
|
|
|
reply(who_e, &m);
|
2005-10-12 17:07:38 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
/*===========================================================================*
|
|
|
|
* sef_local_startup *
|
|
|
|
*===========================================================================*/
|
|
|
|
PRIVATE void sef_local_startup()
|
|
|
|
{
|
|
|
|
/* No live update support for now. */
|
|
|
|
|
|
|
|
/* Let SEF perform startup. */
|
|
|
|
sef_startup();
|
|
|
|
}
|
|
|
|
|
2009-12-11 01:08:19 +01:00
|
|
|
/*===========================================================================*
|
|
|
|
* exec_image_copy *
|
|
|
|
*===========================================================================*/
|
|
|
|
PRIVATE void exec_image_copy(boot_proc_idx, ip, rp)
|
|
|
|
int boot_proc_idx;
|
|
|
|
struct boot_image *ip;
|
|
|
|
struct rproc *rp;
|
|
|
|
{
|
|
|
|
/* Copy the executable image of the given boot process. */
|
|
|
|
int s;
|
|
|
|
struct exec header;
|
|
|
|
static char *boot_image_ptr = NULL;
|
|
|
|
|
|
|
|
if(boot_image_ptr == NULL) {
|
|
|
|
boot_image_ptr = boot_image_buffer;
|
|
|
|
}
|
|
|
|
s = NO_NUM;
|
|
|
|
|
|
|
|
/* Get a.out header. */
|
|
|
|
if(boot_image_buffer+boot_image_buffer_size - boot_image_ptr < sizeof(header)
|
|
|
|
|| (s = sys_getaoutheader(&header, boot_proc_idx)) != OK) {
|
|
|
|
panic("RS", "unable to get copy of a.out header", s);
|
|
|
|
}
|
|
|
|
memcpy(boot_image_ptr, &header, header.a_hdrlen);
|
|
|
|
boot_image_ptr += header.a_hdrlen;
|
|
|
|
|
|
|
|
/* Get text segment. */
|
|
|
|
if(boot_image_buffer+boot_image_buffer_size - boot_image_ptr < header.a_text
|
|
|
|
|| (s = rs_startup_segcopy(ip->endpoint, T, D, (vir_bytes) boot_image_ptr,
|
|
|
|
header.a_text)) != OK) {
|
|
|
|
panic("RS", "unable to get copy of text segment", s);
|
|
|
|
}
|
|
|
|
boot_image_ptr += header.a_text;
|
|
|
|
|
|
|
|
/* Get data segment. */
|
|
|
|
if(boot_image_buffer+boot_image_buffer_size - boot_image_ptr < header.a_data
|
|
|
|
|| (s = rs_startup_segcopy(ip->endpoint, D, D, (vir_bytes) boot_image_ptr,
|
|
|
|
header.a_data)) != OK) {
|
|
|
|
panic("RS", "unable to get copy of data segment", s);
|
|
|
|
}
|
|
|
|
boot_image_ptr += header.a_data;
|
|
|
|
|
|
|
|
/* Set the executable image for the given boot process. */
|
|
|
|
rp->r_exec_len = header.a_hdrlen + header.a_text + header.a_data;
|
|
|
|
rp->r_exec = boot_image_ptr - rp->r_exec_len;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* boot_image_info_lookup *
|
|
|
|
*===========================================================================*/
|
|
|
|
PRIVATE void boot_image_info_lookup(endpoint, image, ip, pp, sp, dp)
|
|
|
|
endpoint_t endpoint;
|
|
|
|
struct boot_image *image;
|
|
|
|
struct boot_image **ip;
|
|
|
|
struct boot_image_priv **pp;
|
|
|
|
struct boot_image_sys **sp;
|
|
|
|
struct boot_image_dev **dp;
|
|
|
|
{
|
|
|
|
/* Lookup entries in boot image tables. */
|
|
|
|
int i;
|
|
|
|
|
|
|
|
/* When requested, locate the corresponding entry in the boot image table
|
|
|
|
* or panic if not found.
|
|
|
|
*/
|
|
|
|
if(ip) {
|
|
|
|
for (i=0; i < NR_BOOT_PROCS; i++) {
|
|
|
|
if(image[i].endpoint == endpoint) {
|
|
|
|
*ip = &image[i];
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if(i == NR_BOOT_PROCS) {
|
|
|
|
panic("RS", "boot image table lookup failed", NO_NUM);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* When requested, locate the corresponding entry in the boot image priv table
|
|
|
|
* or panic if not found.
|
|
|
|
*/
|
|
|
|
if(pp) {
|
|
|
|
for (i=0; boot_image_priv_table[i].endpoint != NULL_BOOT_NR; i++) {
|
|
|
|
if(boot_image_priv_table[i].endpoint == endpoint) {
|
|
|
|
*pp = &boot_image_priv_table[i];
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if(i == NULL_BOOT_NR) {
|
|
|
|
panic("RS", "boot image priv table lookup failed", NO_NUM);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* When requested, locate the corresponding entry in the boot image sys table
|
|
|
|
* or resort to the default entry if not found.
|
|
|
|
*/
|
|
|
|
if(sp) {
|
|
|
|
for (i=0; boot_image_sys_table[i].endpoint != DEFAULT_BOOT_NR; i++) {
|
|
|
|
if(boot_image_sys_table[i].endpoint == endpoint) {
|
|
|
|
*sp = &boot_image_sys_table[i];
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if(boot_image_sys_table[i].endpoint == DEFAULT_BOOT_NR) {
|
|
|
|
*sp = &boot_image_sys_table[i]; /* accept the default entry */
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* When requested, locate the corresponding entry in the boot image dev table
|
|
|
|
* or resort to the default entry if not found.
|
|
|
|
*/
|
|
|
|
if(dp) {
|
|
|
|
for (i=0; boot_image_dev_table[i].endpoint != DEFAULT_BOOT_NR; i++) {
|
|
|
|
if(boot_image_dev_table[i].endpoint == endpoint) {
|
|
|
|
*dp = &boot_image_dev_table[i];
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if(boot_image_dev_table[i].endpoint == DEFAULT_BOOT_NR) {
|
|
|
|
*dp = &boot_image_dev_table[i]; /* accept the default entry */
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* fill_call_mask *
|
|
|
|
*===========================================================================*/
|
|
|
|
PRIVATE void fill_call_mask(calls, tot_nr_calls, call_mask, call_base)
|
|
|
|
int *calls; /* the unordered set of calls */
|
|
|
|
int tot_nr_calls; /* the total number of calls */
|
|
|
|
bitchunk_t *call_mask; /* the call mask to fill in */
|
|
|
|
int call_base; /* the base offset for the calls */
|
|
|
|
{
|
|
|
|
/* Fill a call mask from an unordered set of calls. */
|
|
|
|
int i;
|
|
|
|
bitchunk_t fv;
|
|
|
|
int call_mask_size, nr_calls;
|
|
|
|
|
|
|
|
call_mask_size = BITMAP_CHUNKS(tot_nr_calls);
|
|
|
|
|
|
|
|
/* Count the number of calls to fill in. */
|
|
|
|
nr_calls = 0;
|
|
|
|
for(i=0; calls[i] != SYS_NULL_C; i++) {
|
|
|
|
nr_calls++;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* See if all calls are allowed and call mask must be completely filled. */
|
|
|
|
fv = 0;
|
|
|
|
if(nr_calls == 1 && calls[0] == SYS_ALL_C) {
|
|
|
|
fv = (~0);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Fill or clear call mask. */
|
|
|
|
for(i=0; i < call_mask_size; i++) {
|
|
|
|
call_mask[i] = fv;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Not all calls allowed? Enter calls bit by bit. */
|
|
|
|
if(!fv) {
|
|
|
|
for(i=0; i < nr_calls; i++) {
|
|
|
|
SET_BIT(call_mask, calls[i] - call_base);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2005-10-12 17:07:38 +02:00
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* init_server *
|
|
|
|
*===========================================================================*/
|
|
|
|
PRIVATE void init_server(void)
|
|
|
|
{
|
|
|
|
/* Initialize the reincarnation server. */
|
|
|
|
struct sigaction sa;
|
|
|
|
struct boot_image *ip;
|
2009-12-11 01:08:19 +01:00
|
|
|
int s,i,j;
|
|
|
|
int nr_image_srvs, nr_image_priv_srvs;
|
|
|
|
struct rproc *rp;
|
|
|
|
struct boot_image image[NR_BOOT_PROCS];
|
|
|
|
struct mproc mproc[NR_PROCS];
|
|
|
|
struct exec header;
|
|
|
|
struct boot_image_priv *boot_image_priv;
|
|
|
|
struct boot_image_sys *boot_image_sys;
|
|
|
|
struct boot_image_dev *boot_image_dev;
|
|
|
|
|
|
|
|
/* See if we run in verbose mode. */
|
|
|
|
env_parse("rs_verbose", "d", 0, &rs_verbose, 0, 1);
|
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
/* Initialize the global update descriptor. */
|
|
|
|
rupdate.flags = 0;
|
|
|
|
|
2009-12-11 01:08:19 +01:00
|
|
|
/* Get a copy of the boot image table. */
|
|
|
|
if ((s = sys_getimage(image)) != OK) {
|
|
|
|
panic("RS", "unable to get copy of boot image table", s);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Determine the number of system services in the boot image table and
|
|
|
|
* compute the size required for the boot image buffer.
|
|
|
|
*/
|
|
|
|
nr_image_srvs = 0;
|
|
|
|
boot_image_buffer_size = 0;
|
|
|
|
for(i=0;i<NR_BOOT_PROCS;i++) {
|
|
|
|
ip = &image[i];
|
|
|
|
|
|
|
|
/* System services only. */
|
|
|
|
if(!isbootsrvprocn(_ENDPOINT_P(ip->endpoint))) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
nr_image_srvs++;
|
|
|
|
|
|
|
|
/* Lookup the corresponding entry in the boot image sys table. */
|
|
|
|
boot_image_info_lookup(ip->endpoint, image,
|
|
|
|
NULL, NULL, &boot_image_sys, NULL);
|
|
|
|
|
|
|
|
/* If we must keep a copy of this system service, read the header
|
|
|
|
* and increase the size of the boot image buffer.
|
|
|
|
*/
|
|
|
|
if(boot_image_sys->flags & SF_USE_COPY) {
|
|
|
|
if((s = sys_getaoutheader(&header, i)) != OK) {
|
|
|
|
panic("RS", "unable to get copy of a.out header", s);
|
|
|
|
}
|
|
|
|
boot_image_buffer_size += header.a_hdrlen
|
|
|
|
+ header.a_text + header.a_data;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Determine the number of entries in the boot image priv table and make sure
|
|
|
|
* it matches the number of system services in the boot image table.
|
|
|
|
*/
|
|
|
|
nr_image_priv_srvs = 0;
|
|
|
|
for (i=0; boot_image_priv_table[i].endpoint != NULL_BOOT_NR; i++) {
|
|
|
|
boot_image_priv = &boot_image_priv_table[i];
|
|
|
|
|
|
|
|
/* System services only. */
|
|
|
|
if(!isbootsrvprocn(_ENDPOINT_P(boot_image_priv->endpoint))) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
nr_image_priv_srvs++;
|
|
|
|
}
|
|
|
|
if(nr_image_srvs != nr_image_priv_srvs) {
|
|
|
|
panic("RS", "boot image table and boot image priv table mismatch",
|
|
|
|
NO_NUM);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Allocate boot image buffer. */
|
|
|
|
if(boot_image_buffer_size > 0) {
|
|
|
|
boot_image_buffer = rs_startup_sbrk(boot_image_buffer_size);
|
|
|
|
if(boot_image_buffer == (char *) -1) {
|
|
|
|
panic("RS", "unable to allocate boot image buffer", NO_NUM);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Initialize the system process table in 3 steps, each of them following
|
|
|
|
* the appearance of system services in the boot image priv table.
|
|
|
|
* - Step 1: get a copy of the executable image of every system service that
|
|
|
|
* requires it while it is not yet running.
|
|
|
|
* In addition, set priviliges, sys properties, and dev properties (if any)
|
|
|
|
* for every system service.
|
|
|
|
*/
|
|
|
|
for (i=0; boot_image_priv_table[i].endpoint != NULL_BOOT_NR; i++) {
|
|
|
|
boot_image_priv = &boot_image_priv_table[i];
|
|
|
|
|
|
|
|
/* System services only. */
|
|
|
|
if(!isbootsrvprocn(_ENDPOINT_P(boot_image_priv->endpoint))) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Lookup the corresponding entries in other tables. */
|
|
|
|
boot_image_info_lookup(boot_image_priv->endpoint, image,
|
|
|
|
&ip, NULL, &boot_image_sys, &boot_image_dev);
|
|
|
|
rp = &rproc[boot_image_priv - boot_image_priv_table];
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Get a copy of the executable image if required.
|
|
|
|
*/
|
|
|
|
rp->r_exec_len = 0;
|
|
|
|
rp->r_exec = NULL;
|
|
|
|
if(boot_image_sys->flags & SF_USE_COPY) {
|
|
|
|
exec_image_copy(ip - image, ip, rp);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Set privileges.
|
|
|
|
* XXX FIXME: We should also let RS set vm calls allowed for each sys
|
|
|
|
* service by using vm_set_priv(). We need a more uniform privilege
|
|
|
|
* management scheme in VM for this change.
|
|
|
|
*/
|
2009-12-23 15:05:20 +01:00
|
|
|
/* Get label. */
|
|
|
|
strcpy(rp->r_label, boot_image_priv->label);
|
|
|
|
|
2009-12-11 01:08:19 +01:00
|
|
|
/* Force a static privilege id for system services in the boot image. */
|
|
|
|
rp->r_priv.s_id = static_priv_id(_ENDPOINT_P(boot_image_priv->endpoint));
|
|
|
|
|
|
|
|
/* Initialize privilege bitmaps. */
|
|
|
|
rp->r_priv.s_flags = boot_image_priv->flags; /* privilege flags */
|
|
|
|
rp->r_priv.s_trap_mask = boot_image_priv->trap_mask; /* allowed traps */
|
|
|
|
memcpy(&rp->r_priv.s_ipc_to, &boot_image_priv->ipc_to,
|
|
|
|
sizeof(rp->r_priv.s_ipc_to)); /* allowed targets */
|
|
|
|
|
|
|
|
/* Initialize call mask bitmap from unordered set. */
|
|
|
|
fill_call_mask(boot_image_priv->k_calls, NR_SYS_CALLS,
|
|
|
|
rp->r_priv.s_k_call_mask, KERNEL_CALL);
|
|
|
|
|
|
|
|
/* Set the privilege structure. */
|
|
|
|
if ((s = sys_privctl(ip->endpoint, SYS_PRIV_SET_SYS, &(rp->r_priv)))
|
|
|
|
!= OK) {
|
|
|
|
panic("RS", "unable to set privilege structure", s);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Synch the privilege structure with the kernel. */
|
|
|
|
if ((s = sys_getpriv(&(rp->r_priv), ip->endpoint)) != OK) {
|
|
|
|
panic("RS", "unable to synch privilege structure", s);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Set sys properties.
|
|
|
|
*/
|
|
|
|
rp->r_sys_flags = boot_image_sys->flags; /* sys flags */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Set dev properties.
|
|
|
|
*/
|
|
|
|
rp->r_dev_nr = boot_image_dev->dev_nr; /* major device number */
|
|
|
|
rp->r_dev_style = boot_image_dev->dev_style; /* device style */
|
|
|
|
rp->r_period = boot_image_dev->period; /* heartbeat period */
|
2009-12-17 02:53:26 +01:00
|
|
|
|
2009-12-23 15:05:20 +01:00
|
|
|
/* Get process name. */
|
|
|
|
strcpy(rp->r_proc_name, ip->proc_name);
|
2009-12-17 02:53:26 +01:00
|
|
|
|
|
|
|
/* Get command settings. */
|
|
|
|
rp->r_cmd[0]= '\0';
|
|
|
|
rp->r_argv[0] = rp->r_cmd;
|
|
|
|
rp->r_argv[1] = NULL;
|
|
|
|
rp->r_argc = 1;
|
|
|
|
rp->r_script[0]= '\0';
|
|
|
|
|
|
|
|
/* Get some settings from the boot image table. */
|
|
|
|
rp->r_nice = ip->priority;
|
|
|
|
rp->r_proc_nr_e = ip->endpoint;
|
|
|
|
|
|
|
|
/* Set some defaults. */
|
|
|
|
rp->r_uid = 0; /* root */
|
|
|
|
rp->r_check_tm = 0; /* not checked yet */
|
|
|
|
getuptime(&rp->r_alive_tm); /* currently alive */
|
|
|
|
rp->r_stop_tm = 0; /* not exiting yet */
|
|
|
|
rp->r_restarts = 0; /* no restarts so far */
|
|
|
|
rp->r_set_resources = 0; /* don't set resources */
|
|
|
|
|
|
|
|
/* Mark as in use. */
|
|
|
|
rp->r_flags = RS_IN_USE;
|
|
|
|
rproc_ptr[_ENDPOINT_P(rp->r_proc_nr_e)]= rp;
|
2009-12-11 01:08:19 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/* - Step 2: allow every system service in the boot image to run.
|
|
|
|
*/
|
|
|
|
for (i=0; boot_image_priv_table[i].endpoint != NULL_BOOT_NR; i++) {
|
|
|
|
boot_image_priv = &boot_image_priv_table[i];
|
|
|
|
|
|
|
|
/* System services only. */
|
|
|
|
if(!isbootsrvprocn(_ENDPOINT_P(boot_image_priv->endpoint))) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Lookup the corresponding entry in the boot image table. */
|
|
|
|
boot_image_info_lookup(boot_image_priv->endpoint, image,
|
|
|
|
&ip, NULL, NULL, NULL);
|
|
|
|
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
/* Allow the service to run. */
|
2009-12-11 01:08:19 +01:00
|
|
|
if ((s = sys_privctl(ip->endpoint, SYS_PRIV_ALLOW, NULL)) != OK) {
|
|
|
|
panic("RS", "unable to initialize privileges", s);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-12-17 02:53:26 +01:00
|
|
|
/* - Step 3: all the system services in the boot image are now running.
|
|
|
|
* Complete the initialization of the system process table in collaboration
|
|
|
|
* with other system processes.
|
2009-12-11 01:08:19 +01:00
|
|
|
*/
|
|
|
|
if ((s = getsysinfo(PM_PROC_NR, SI_PROC_TAB, mproc)) != OK) {
|
|
|
|
panic("RS", "unable to get copy of PM process table", s);
|
|
|
|
}
|
|
|
|
for (i=0; boot_image_priv_table[i].endpoint != NULL_BOOT_NR; i++) {
|
|
|
|
boot_image_priv = &boot_image_priv_table[i];
|
|
|
|
|
|
|
|
/* System services only. */
|
|
|
|
if(!isbootsrvprocn(_ENDPOINT_P(boot_image_priv->endpoint))) {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2009-12-17 02:53:26 +01:00
|
|
|
/* Lookup the corresponding slot in the system process table. */
|
2009-12-11 01:08:19 +01:00
|
|
|
rp = &rproc[boot_image_priv - boot_image_priv_table];
|
|
|
|
|
|
|
|
/* Get pid from PM process table. */
|
|
|
|
rp->r_pid = NO_PID;
|
|
|
|
for (j = 0; j < NR_PROCS; j++) {
|
|
|
|
if (mproc[j].mp_endpoint == rp->r_proc_nr_e) {
|
|
|
|
rp->r_pid = mproc[j].mp_pid;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if(j == NR_PROCS) {
|
|
|
|
panic("RS", "unable to get pid", NO_NUM);
|
|
|
|
}
|
|
|
|
|
2009-12-17 02:53:26 +01:00
|
|
|
/* Publish the new system service.
|
|
|
|
* XXX FIXME. Possible race condition. We should publish labels before
|
|
|
|
* allowing other processes to run.
|
|
|
|
*/
|
2009-12-11 01:08:19 +01:00
|
|
|
s = publish_service(rp);
|
|
|
|
if (s != OK) {
|
|
|
|
panic("RS", "unable to publish boot system service", s);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Now complete RS initialization process in collaboration with other
|
|
|
|
* system services.
|
|
|
|
*/
|
|
|
|
/* Let the rest of the system know about our dynamically allocated buffer. */
|
|
|
|
if(boot_image_buffer_size > 0) {
|
|
|
|
boot_image_buffer = rs_startup_sbrk_synch(boot_image_buffer_size);
|
|
|
|
if(boot_image_buffer == (char *) -1) {
|
|
|
|
panic("RS", "unable to synch boot image buffer", NO_NUM);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Set alarm to periodically check service status. */
|
|
|
|
if (OK != (s=sys_setalarm(RS_DELTA_T, 0)))
|
|
|
|
panic("RS", "couldn't set alarm", s);
|
2005-10-12 17:07:38 +02:00
|
|
|
|
|
|
|
/* Install signal handlers. Ask PM to transform signal into message. */
|
|
|
|
sa.sa_handler = SIG_MESS;
|
|
|
|
sigemptyset(&sa.sa_mask);
|
|
|
|
sa.sa_flags = 0;
|
|
|
|
if (sigaction(SIGCHLD,&sa,NULL)<0) panic("RS","sigaction failed", errno);
|
|
|
|
if (sigaction(SIGTERM,&sa,NULL)<0) panic("RS","sigaction failed", errno);
|
|
|
|
|
2007-04-23 16:43:25 +02:00
|
|
|
/* Initialize the exec pipe. */
|
|
|
|
if (pipe(exec_pipe) == -1)
|
|
|
|
panic("RS", "pipe failed", errno);
|
|
|
|
if (fcntl(exec_pipe[0], F_SETFD,
|
|
|
|
fcntl(exec_pipe[0], F_GETFD) | FD_CLOEXEC) == -1)
|
|
|
|
{
|
|
|
|
panic("RS", "fcntl set FD_CLOEXEC on pipe input failed", errno);
|
|
|
|
}
|
|
|
|
if (fcntl(exec_pipe[1], F_SETFD,
|
|
|
|
fcntl(exec_pipe[1], F_GETFD) | FD_CLOEXEC) == -1)
|
|
|
|
{
|
|
|
|
panic("RS", "fcntl set FD_CLOEXEC on pipe output failed", errno);
|
|
|
|
}
|
|
|
|
if (fcntl(exec_pipe[0], F_SETFL,
|
|
|
|
fcntl(exec_pipe[0], F_GETFL) | O_NONBLOCK) == -1)
|
|
|
|
{
|
|
|
|
panic("RS", "fcntl set O_NONBLOCK on pipe input failed", errno);
|
|
|
|
}
|
2009-12-11 01:08:19 +01:00
|
|
|
|
|
|
|
/* Map out our own text and data. This is normally done in crtso.o
|
|
|
|
* but RS is an exception - we don't get to talk to VM so early on.
|
|
|
|
* That's why we override munmap() and munmap_text() in utility.c.
|
|
|
|
*
|
|
|
|
* _minix_unmapzero() is the same code in crtso.o that normally does
|
|
|
|
* it on startup. It's best that it's there as crtso.o knows exactly
|
|
|
|
* what the ranges are of the filler data.
|
|
|
|
*/
|
|
|
|
unmap_ok = 1;
|
|
|
|
_minix_unmapzero();
|
2005-10-12 17:07:38 +02:00
|
|
|
}
|
|
|
|
|
2006-03-10 17:10:05 +01:00
|
|
|
/*===========================================================================*
|
|
|
|
* sig_handler *
|
|
|
|
*===========================================================================*/
|
|
|
|
PRIVATE void sig_handler()
|
|
|
|
{
|
|
|
|
sigset_t sigset;
|
|
|
|
int sig;
|
|
|
|
|
|
|
|
/* Try to obtain signal set from PM. */
|
|
|
|
if (getsigset(&sigset) != 0) return;
|
|
|
|
|
|
|
|
/* Check for known signals. */
|
|
|
|
if (sigismember(&sigset, SIGCHLD)) do_exit(NULL);
|
|
|
|
if (sigismember(&sigset, SIGTERM)) do_shutdown(NULL);
|
|
|
|
}
|
2005-10-12 17:07:38 +02:00
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* get_work *
|
|
|
|
*===========================================================================*/
|
|
|
|
PRIVATE void get_work(m_in)
|
|
|
|
message *m_in; /* pointer to message */
|
|
|
|
{
|
|
|
|
int s; /* receive status */
|
Basic System Event Framework (SEF) with ping and live update.
SYSLIB CHANGES:
- SEF must be used by every system process and is thereby part of the system
library.
- The framework provides a receive() interface (sef_receive) for system
processes to automatically catch known system even messages and process them.
- SEF provides a default behavior for each type of system event, but allows
system processes to register callbacks to override the default behavior.
- Custom (local to the process) or predefined (provided by SEF) callback
implementations can be registered to SEF.
- SEF currently includes support for 2 types of system events:
1. SEF Ping. The event occurs every time RS sends a ping to figure out
whether a system process is still alive. The default callback implementation
provided by SEF is to notify RS back to let it know the process is alive
and kicking.
2. SEF Live update. The event occurs every time RS sends a prepare to update
message to let a system process know an update is available and to prepare
for it. The live update support is very basic for now. SEF only deals with
verifying if the prepare state can be supported by the process, dumping the
state for debugging purposes, and providing an event-driven programming
model to the process to react to state changes check-in when ready to update.
- SEF should be extended in the future to integrate support for more types of
system events. Ideally, all the cross-cutting concerns should be integrated into
SEF to avoid duplicating code and ease extensibility. Examples include:
* PM notify messages primarily used at shutdown.
* SYSTEM notify messages primarily used for signals.
* CLOCK notify messages used for system alarms.
* Debug messages. IS could still be in charge of fkey handling but would
forward the debug message to the target process (e.g. PM, if the user
requested debug information about PM). SEF would then catch the message and
do nothing unless the process has registered an appropriate callback to
deal with the event. This simplifies the programming model to print debug
information, avoids duplicating code, and reduces the effort to print
debug information.
SYSTEM PROCESSES CHANGES:
- Every system process registers SEF callbacks it needs to override the default
system behavior and calls sef_startup() right after being started.
- sef_startup() does almost nothing now, but will be extended in the future to
support callbacks of its own to let RS control and synchronize with every
system process at initialization time.
- Every system process calls sef_receive() now rather than receive() directly,
to let SEF handle predefined system events.
RS CHANGES:
- RS supports a basic single-component live update protocol now, as follows:
* When an update command is issued (via "service update *"), RS notifies the
target system process to prepare for a specific update state.
* If the process doesn't respond back in time, the update is aborted.
* When the process responds back, RS kills it and marks it for refreshing.
* The process is then automatically restarted as for a buggy process and can
start running again.
* Live update is currently prototyped as a controlled failure.
2009-12-21 15:12:21 +01:00
|
|
|
if (OK != (s=sef_receive(ANY, m_in))) /* wait for message */
|
|
|
|
panic("RS", "sef_receive failed", s);
|
2005-10-12 17:07:38 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* reply *
|
|
|
|
*===========================================================================*/
|
2006-10-25 15:40:36 +02:00
|
|
|
PRIVATE void reply(who, m_out)
|
2005-10-12 17:07:38 +02:00
|
|
|
int who; /* replyee */
|
2006-10-25 15:40:36 +02:00
|
|
|
message *m_out; /* reply message */
|
2005-10-12 17:07:38 +02:00
|
|
|
{
|
|
|
|
int s; /* send status */
|
|
|
|
|
2008-02-21 17:20:22 +01:00
|
|
|
s = sendnb(who, m_out); /* send the message */
|
|
|
|
if (s != OK)
|
|
|
|
printf("RS: unable to send reply to %d: %d\n", who, s);
|
2005-10-12 17:07:38 +02:00
|
|
|
}
|
|
|
|
|