2009-12-11 01:08:19 +01:00
|
|
|
/* This file contains the definition of the boot image info tables.
|
|
|
|
|
*
|
|
|
|
|
* Changes:
|
|
|
|
|
* Nov 22, 2009: Created (Cristiano Giuffrida)
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#define _TABLE
|
|
|
|
|
|
|
|
|
|
#include "inc.h"
|
|
|
|
|
|
Initialization protocol for system services.
SYSLIB CHANGES:
- SEF framework now supports a new SEF Init request type from RS. 3 different
callbacks are available (init_fresh, init_lu, init_restart) to specify
initialization code when a service starts fresh, starts after a live update,
or restarts.
SYSTEM SERVICE CHANGES:
- Initialization code for system services is now enclosed in a callback SEF will
automatically call at init time. The return code of the callback will
tell RS whether the initialization completed successfully.
- Each init callback can access information passed by RS to initialize. As of
now, each system service has access to the public entries of RS's system process
table to gather all the information required to initialize. This design
eliminates many existing or potential races at boot time and provides a uniform
initialization interface to system services. The same interface will be reused
for the upcoming publish/subscribe model to handle dynamic
registration / deregistration of system services.
VM CHANGES:
- Uniform privilege management for all system services. Every service uses the
same call mask format. For boot services, VM copies the call mask from init
data. For dynamic services, VM still receives the call mask via rs_set_priv
call that will be soon replaced by the upcoming publish/subscribe model.
RS CHANGES:
- The system process table has been reorganized and split into private entries
and public entries. Only the latter ones are exposed to system services.
- VM call masks are now entirely configured in rs/table.c
- RS has now its own slot in the system process table. Only kernel tasks and
user processes not included in the boot image are now left out from the system
process table.
- RS implements the initialization protocol for system services.
- For services in the boot image, RS blocks till initialization is complete and
panics when failure is reported back. Services are initialized in their order of
appearance in the boot image priv table and RS blocks to implements synchronous
initialization for every system service having the flag SF_SYNCH_BOOT set.
- For services started dynamically, the initialization protocol is implemented
as though it were the first ping for the service. In this case, if the
system service fails to report back (or reports failure), RS brings the service
down rather than trying to restart it.
2010-01-08 02:20:42 +01:00
|
|
|
/* Definition of the boot image priv table. The order of entries in this table
|
|
|
|
|
* reflects the order boot system services are made runnable and initialized
|
2010-07-13 17:30:17 +02:00
|
|
|
* at boot time.
|
Initialization protocol for system services.
SYSLIB CHANGES:
- SEF framework now supports a new SEF Init request type from RS. 3 different
callbacks are available (init_fresh, init_lu, init_restart) to specify
initialization code when a service starts fresh, starts after a live update,
or restarts.
SYSTEM SERVICE CHANGES:
- Initialization code for system services is now enclosed in a callback SEF will
automatically call at init time. The return code of the callback will
tell RS whether the initialization completed successfully.
- Each init callback can access information passed by RS to initialize. As of
now, each system service has access to the public entries of RS's system process
table to gather all the information required to initialize. This design
eliminates many existing or potential races at boot time and provides a uniform
initialization interface to system services. The same interface will be reused
for the upcoming publish/subscribe model to handle dynamic
registration / deregistration of system services.
VM CHANGES:
- Uniform privilege management for all system services. Every service uses the
same call mask format. For boot services, VM copies the call mask from init
data. For dynamic services, VM still receives the call mask via rs_set_priv
call that will be soon replaced by the upcoming publish/subscribe model.
RS CHANGES:
- The system process table has been reorganized and split into private entries
and public entries. Only the latter ones are exposed to system services.
- VM call masks are now entirely configured in rs/table.c
- RS has now its own slot in the system process table. Only kernel tasks and
user processes not included in the boot image are now left out from the system
process table.
- RS implements the initialization protocol for system services.
- For services in the boot image, RS blocks till initialization is complete and
panics when failure is reported back. Services are initialized in their order of
appearance in the boot image priv table and RS blocks to implements synchronous
initialization for every system service having the flag SF_SYNCH_BOOT set.
- For services started dynamically, the initialization protocol is implemented
as though it were the first ping for the service. In this case, if the
system service fails to report back (or reports failure), RS brings the service
down rather than trying to restart it.
2010-01-08 02:20:42 +01:00
|
|
|
*/
|
2012-03-25 20:25:53 +02:00
|
|
|
struct boot_image_priv boot_image_priv_table[] = {
|
2010-07-13 23:11:44 +02:00
|
|
|
/*endpoint, label, flags, */
|
|
|
|
|
{RS_PROC_NR, "rs", RSYS_F },
|
|
|
|
|
{VM_PROC_NR, "vm", VM_F },
|
|
|
|
|
{PM_PROC_NR, "pm", SRV_F },
|
|
|
|
|
{SCHED_PROC_NR,"sched", SRV_F },
|
|
|
|
|
{VFS_PROC_NR, "vfs", SRV_F },
|
|
|
|
|
{DS_PROC_NR, "ds", SRV_F },
|
|
|
|
|
{TTY_PROC_NR, "tty", SRV_F },
|
|
|
|
|
{MEM_PROC_NR, "memory", SRV_F },
|
|
|
|
|
{MFS_PROC_NR,"fs_imgrd", SRV_F },
|
|
|
|
|
{PFS_PROC_NR, "pfs", SRV_F },
|
|
|
|
|
{INIT_PROC_NR, "init", USR_F },
|
|
|
|
|
{NULL_BOOT_NR, "", 0, } /* null entry */
|
2009-12-11 01:08:19 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/* Definition of the boot image sys table. */
|
2012-03-25 20:25:53 +02:00
|
|
|
struct boot_image_sys boot_image_sys_table[] = {
|
2009-12-23 15:05:20 +01:00
|
|
|
/*endpoint, flags */
|
2010-04-27 13:17:30 +02:00
|
|
|
{ RS_PROC_NR, SRVR_SF },
|
Initialization protocol for system services.
SYSLIB CHANGES:
- SEF framework now supports a new SEF Init request type from RS. 3 different
callbacks are available (init_fresh, init_lu, init_restart) to specify
initialization code when a service starts fresh, starts after a live update,
or restarts.
SYSTEM SERVICE CHANGES:
- Initialization code for system services is now enclosed in a callback SEF will
automatically call at init time. The return code of the callback will
tell RS whether the initialization completed successfully.
- Each init callback can access information passed by RS to initialize. As of
now, each system service has access to the public entries of RS's system process
table to gather all the information required to initialize. This design
eliminates many existing or potential races at boot time and provides a uniform
initialization interface to system services. The same interface will be reused
for the upcoming publish/subscribe model to handle dynamic
registration / deregistration of system services.
VM CHANGES:
- Uniform privilege management for all system services. Every service uses the
same call mask format. For boot services, VM copies the call mask from init
data. For dynamic services, VM still receives the call mask via rs_set_priv
call that will be soon replaced by the upcoming publish/subscribe model.
RS CHANGES:
- The system process table has been reorganized and split into private entries
and public entries. Only the latter ones are exposed to system services.
- VM call masks are now entirely configured in rs/table.c
- RS has now its own slot in the system process table. Only kernel tasks and
user processes not included in the boot image are now left out from the system
process table.
- RS implements the initialization protocol for system services.
- For services in the boot image, RS blocks till initialization is complete and
panics when failure is reported back. Services are initialized in their order of
appearance in the boot image priv table and RS blocks to implements synchronous
initialization for every system service having the flag SF_SYNCH_BOOT set.
- For services started dynamically, the initialization protocol is implemented
as though it were the first ping for the service. In this case, if the
system service fails to report back (or reports failure), RS brings the service
down rather than trying to restart it.
2010-01-08 02:20:42 +01:00
|
|
|
{ VM_PROC_NR, VM_SF },
|
2010-04-27 13:17:30 +02:00
|
|
|
{ PM_PROC_NR, SRVR_SF },
|
|
|
|
|
{ VFS_PROC_NR, SRVR_SF },
|
2010-07-05 21:37:08 +02:00
|
|
|
{ MFS_PROC_NR, 0 },
|
|
|
|
|
{ PFS_PROC_NR, SRV_SF },
|
2009-12-11 01:08:19 +01:00
|
|
|
{ DEFAULT_BOOT_NR, SRV_SF } /* default entry */
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/* Definition of the boot image dev table. */
|
2012-03-25 20:25:53 +02:00
|
|
|
struct boot_image_dev boot_image_dev_table[] = {
|
2010-04-09 23:56:44 +02:00
|
|
|
/*endpoint, flags, dev_nr, dev_style, dev_style2 */
|
|
|
|
|
{ TTY_PROC_NR, SRV_DF, TTY_MAJOR, STYLE_TTY, STYLE_CTTY },
|
|
|
|
|
{ MEM_PROC_NR, SRV_DF, MEMORY_MAJOR, STYLE_DEV, STYLE_NDEV },
|
|
|
|
|
{ DEFAULT_BOOT_NR, SRV_DF, 0, STYLE_NDEV, STYLE_NDEV } /* default
|
|
|
|
|
* entry
|
|
|
|
|
*/
|
2009-12-11 01:08:19 +01:00
|
|
|
};
|
|
|
|
|
|
