2005-12-02 15:45:10 +01:00
|
|
|
/*
|
|
|
|
|
main.c
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include "../drivers.h"
|
|
|
|
|
|
2006-10-20 17:01:32 +02:00
|
|
|
#include <minix/rs.h>
|
2009-09-29 20:47:56 +02:00
|
|
|
#include <minix/endpoint.h>
|
2005-12-02 15:45:10 +01:00
|
|
|
|
2006-01-12 15:46:12 +01:00
|
|
|
#include "pci.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
|
|
|
PUBLIC struct pci_acl pci_acl[NR_DRIVERS];
|
2006-10-20 17:01:32 +02:00
|
|
|
|
2005-12-02 15:45:10 +01:00
|
|
|
FORWARD _PROTOTYPE( void do_init, (message *mp) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_first_dev, (message *mp) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_next_dev, (message *mp) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_find_dev, (message *mp) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_ids, (message *mp) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_dev_name, (message *mp) );
|
2006-07-10 14:39:54 +02:00
|
|
|
FORWARD _PROTOTYPE( void do_dev_name_s, (message *mp) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_slot_name_s, (message *mp) );
|
2007-04-23 16:54:51 +02:00
|
|
|
FORWARD _PROTOTYPE( void do_set_acl, (message *mp) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_del_acl, (message *mp) );
|
2005-12-02 15:45:10 +01:00
|
|
|
FORWARD _PROTOTYPE( void do_reserve, (message *mp) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_attr_r8, (message *mp) );
|
2006-01-12 15:46:12 +01:00
|
|
|
FORWARD _PROTOTYPE( void do_attr_r16, (message *mp) );
|
2005-12-02 15:45:10 +01:00
|
|
|
FORWARD _PROTOTYPE( void do_attr_r32, (message *mp) );
|
2006-01-12 15:46:12 +01:00
|
|
|
FORWARD _PROTOTYPE( void do_attr_w8, (message *mp) );
|
|
|
|
|
FORWARD _PROTOTYPE( void do_attr_w16, (message *mp) );
|
2005-12-02 15:45:10 +01:00
|
|
|
FORWARD _PROTOTYPE( void do_attr_w32, (message *mp) );
|
2006-01-12 15:46:12 +01:00
|
|
|
FORWARD _PROTOTYPE( void do_rescan_bus, (message *mp) );
|
2006-10-20 17:01:32 +02:00
|
|
|
FORWARD _PROTOTYPE( void reply, (message *mp, int result) );
|
|
|
|
|
FORWARD _PROTOTYPE( struct rs_pci *find_acl, (int endpoint) );
|
2005-12-02 15:45:10 +01:00
|
|
|
|
2007-02-16 16:50:49 +01:00
|
|
|
extern int debug;
|
|
|
|
|
|
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-12-02 15:45:10 +01:00
|
|
|
int main(void)
|
|
|
|
|
{
|
2006-01-12 15:46:12 +01:00
|
|
|
int i, r;
|
2005-12-02 15:45:10 +01:00
|
|
|
message m;
|
|
|
|
|
|
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-12-02 15:45:10 +01:00
|
|
|
for(;;)
|
|
|
|
|
{
|
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
|
|
|
r= sef_receive(ANY, &m);
|
2005-12-02 15:45:10 +01:00
|
|
|
if (r < 0)
|
|
|
|
|
{
|
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
|
|
|
printf("PCI: sef_receive from ANY failed: %d\n", r);
|
2005-12-02 15:45:10 +01:00
|
|
|
break;
|
|
|
|
|
}
|
2009-09-29 20:47:56 +02:00
|
|
|
|
|
|
|
|
if (is_notify(m.m_type)) {
|
New RS and new signal handling for system processes.
UPDATING INFO:
20100317:
/usr/src/etc/system.conf updated to ignore default kernel calls: copy
it (or merge it) to /etc/system.conf.
The hello driver (/dev/hello) added to the distribution:
# cd /usr/src/commands/scripts && make clean install
# cd /dev && MAKEDEV hello
KERNEL CHANGES:
- Generic signal handling support. The kernel no longer assumes PM as a signal
manager for every process. The signal manager of a given process can now be
specified in its privilege slot. When a signal has to be delivered, the kernel
performs the lookup and forwards the signal to the appropriate signal manager.
PM is the default signal manager for user processes, RS is the default signal
manager for system processes. To enable ptrace()ing for system processes, it
is sufficient to change the default signal manager to PM. This will temporarily
disable crash recovery, though.
- sys_exit() is now split into sys_exit() (i.e. exit() for system processes,
which generates a self-termination signal), and sys_clear() (i.e. used by PM
to ask the kernel to clear a process slot when a process exits).
- Added a new kernel call (i.e. sys_update()) to swap two process slots and
implement live update.
PM CHANGES:
- Posix signal handling is no longer allowed for system processes. System
signals are split into two fixed categories: termination and non-termination
signals. When a non-termination signaled is processed, PM transforms the signal
into an IPC message and delivers the message to the system process. When a
termination signal is processed, PM terminates the process.
- PM no longer assumes itself as the signal manager for system processes. It now
makes sure that every system signal goes through the kernel before being
actually processes. The kernel will then dispatch the signal to the appropriate
signal manager which may or may not be PM.
SYSLIB CHANGES:
- Simplified SEF init and LU callbacks.
- Added additional predefined SEF callbacks to debug crash recovery and
live update.
- Fixed a temporary ack in the SEF init protocol. SEF init reply is now
completely synchronous.
- Added SEF signal event type to provide a uniform interface for system
processes to deal with signals. A sef_cb_signal_handler() callback is
available for system processes to handle every received signal. A
sef_cb_signal_manager() callback is used by signal managers to process
system signals on behalf of the kernel.
- Fixed a few bugs with memory mapping and DS.
VM CHANGES:
- Page faults and memory requests coming from the kernel are now implemented
using signals.
- Added a new VM call to swap two process slots and implement live update.
- The call is used by RS at update time and in turn invokes the kernel call
sys_update().
RS CHANGES:
- RS has been reworked with a better functional decomposition.
- Better kernel call masks. com.h now defines the set of very basic kernel calls
every system service is allowed to use. This makes system.conf simpler and
easier to maintain. In addition, this guarantees a higher level of isolation
for system libraries that use one or more kernel calls internally (e.g. printf).
- RS is the default signal manager for system processes. By default, RS
intercepts every signal delivered to every system process. This makes crash
recovery possible before bringing PM and friends in the loop.
- RS now supports fast rollback when something goes wrong while initializing
the new version during a live update.
- Live update is now implemented by keeping the two versions side-by-side and
swapping the process slots when the old version is ready to update.
- Crash recovery is now implemented by keeping the two versions side-by-side
and cleaning up the old version only when the recovery process is complete.
DS CHANGES:
- Fixed a bug when the process doing ds_publish() or ds_delete() is not known
by DS.
- Fixed the completely broken support for strings. String publishing is now
implemented in the system library and simply wraps publishing of memory ranges.
Ideally, we should adopt a similar approach for other data types as well.
- Test suite fixed.
DRIVER CHANGES:
- The hello driver has been added to the Minix distribution to demonstrate basic
live update and crash recovery functionalities.
- Other drivers have been adapted to conform the new SEF interface.
2010-03-17 02:15:29 +01:00
|
|
|
printf("PCI: got notify from %d\n", m.m_source);
|
2009-09-29 20:47:56 +02:00
|
|
|
|
|
|
|
|
/* done, get a new message */
|
|
|
|
|
continue;
|
|
|
|
|
}
|
|
|
|
|
|
2005-12-02 15:45:10 +01:00
|
|
|
switch(m.m_type)
|
|
|
|
|
{
|
|
|
|
|
case BUSC_PCI_INIT: do_init(&m); break;
|
|
|
|
|
case BUSC_PCI_FIRST_DEV: do_first_dev(&m); break;
|
|
|
|
|
case BUSC_PCI_NEXT_DEV: do_next_dev(&m); break;
|
|
|
|
|
case BUSC_PCI_FIND_DEV: do_find_dev(&m); break;
|
|
|
|
|
case BUSC_PCI_IDS: do_ids(&m); break;
|
|
|
|
|
case BUSC_PCI_DEV_NAME: do_dev_name(&m); break;
|
|
|
|
|
case BUSC_PCI_RESERVE: do_reserve(&m); break;
|
|
|
|
|
case BUSC_PCI_ATTR_R8: do_attr_r8(&m); break;
|
2006-01-12 15:46:12 +01:00
|
|
|
case BUSC_PCI_ATTR_R16: do_attr_r16(&m); break;
|
2005-12-02 15:45:10 +01:00
|
|
|
case BUSC_PCI_ATTR_R32: do_attr_r32(&m); break;
|
2006-01-12 15:46:12 +01:00
|
|
|
case BUSC_PCI_ATTR_W8: do_attr_w8(&m); break;
|
|
|
|
|
case BUSC_PCI_ATTR_W16: do_attr_w16(&m); break;
|
2005-12-02 15:45:10 +01:00
|
|
|
case BUSC_PCI_ATTR_W32: do_attr_w32(&m); break;
|
2006-01-12 15:46:12 +01:00
|
|
|
case BUSC_PCI_RESCAN: do_rescan_bus(&m); break;
|
2006-07-10 14:39:54 +02:00
|
|
|
case BUSC_PCI_DEV_NAME_S: do_dev_name_s(&m); break;
|
|
|
|
|
case BUSC_PCI_SLOT_NAME_S: do_slot_name_s(&m); break;
|
2007-04-23 16:54:51 +02:00
|
|
|
case BUSC_PCI_SET_ACL: do_set_acl(&m); break;
|
|
|
|
|
case BUSC_PCI_DEL_ACL: do_del_acl(&m); break;
|
2005-12-02 15:45:10 +01:00
|
|
|
default:
|
2006-01-12 15:46:12 +01:00
|
|
|
printf("PCI: got message from %d, type %d\n",
|
2005-12-02 15:45:10 +01:00
|
|
|
m.m_source, m.m_type);
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
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()
|
|
|
|
|
{
|
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
|
|
|
/* Register init callbacks. */
|
|
|
|
|
sef_setcb_init_fresh(sef_cb_init_fresh);
|
|
|
|
|
sef_setcb_init_lu(sef_cb_init_fresh);
|
|
|
|
|
sef_setcb_init_restart(sef_cb_init_fresh);
|
|
|
|
|
|
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
|
|
|
/* Register live update callbacks. */
|
|
|
|
|
sef_setcb_lu_prepare(sef_cb_lu_prepare_always_ready);
|
|
|
|
|
sef_setcb_lu_state_isvalid(sef_cb_lu_state_isvalid_standard);
|
|
|
|
|
|
|
|
|
|
/* Let SEF perform startup. */
|
|
|
|
|
sef_startup();
|
|
|
|
|
}
|
|
|
|
|
|
2005-12-02 15:45:10 +01:00
|
|
|
PRIVATE void do_init(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
2007-04-24 14:55:37 +02:00
|
|
|
int r;
|
2005-12-02 15:45:10 +01:00
|
|
|
|
2006-01-18 10:48:32 +01:00
|
|
|
#if DEBUG
|
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
|
|
|
printf("PCI: do_init: called by '%d'\n", mp->m_source);
|
2006-01-18 10:48:32 +01:00
|
|
|
#endif
|
2005-12-02 15:45:10 +01:00
|
|
|
|
|
|
|
|
mp->m_type= 0;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
2007-02-16 16:50:49 +01:00
|
|
|
printf("PCI: do_init: unable to send to %d: %d\n",
|
|
|
|
|
mp->m_source, r);
|
2005-12-02 15:45:10 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void do_first_dev(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
2006-10-20 17:01:32 +02:00
|
|
|
int i, r, devind;
|
2005-12-02 15:45:10 +01:00
|
|
|
u16_t vid, did;
|
2006-10-20 17:01:32 +02:00
|
|
|
struct rs_pci *aclp;
|
|
|
|
|
|
|
|
|
|
aclp= find_acl(mp->m_source);
|
|
|
|
|
|
2007-02-16 16:50:49 +01:00
|
|
|
if (!aclp && debug)
|
|
|
|
|
printf("PCI: do_first_dev: no acl for caller %d\n",
|
|
|
|
|
mp->m_source);
|
2005-12-02 15:45:10 +01:00
|
|
|
|
2006-10-20 17:01:32 +02:00
|
|
|
r= pci_first_dev_a(aclp, &devind, &vid, &did);
|
2005-12-02 15:45:10 +01:00
|
|
|
if (r == 1)
|
|
|
|
|
{
|
|
|
|
|
mp->m1_i1= devind;
|
|
|
|
|
mp->m1_i2= vid;
|
|
|
|
|
mp->m1_i3= did;
|
|
|
|
|
}
|
|
|
|
|
mp->m_type= r;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
2007-02-16 16:50:49 +01:00
|
|
|
printf("PCI: do_first_dev: unable to send to %d: %d\n",
|
2005-12-02 15:45:10 +01:00
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void do_next_dev(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, devind;
|
|
|
|
|
u16_t vid, did;
|
2006-10-20 17:01:32 +02:00
|
|
|
struct rs_pci *aclp;
|
2005-12-02 15:45:10 +01:00
|
|
|
|
|
|
|
|
devind= mp->m1_i1;
|
2006-10-20 17:01:32 +02:00
|
|
|
aclp= find_acl(mp->m_source);
|
2005-12-02 15:45:10 +01:00
|
|
|
|
2006-10-20 17:01:32 +02:00
|
|
|
r= pci_next_dev_a(aclp, &devind, &vid, &did);
|
2005-12-02 15:45:10 +01:00
|
|
|
if (r == 1)
|
|
|
|
|
{
|
|
|
|
|
mp->m1_i1= devind;
|
|
|
|
|
mp->m1_i2= vid;
|
|
|
|
|
mp->m1_i3= did;
|
|
|
|
|
}
|
|
|
|
|
mp->m_type= r;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
2007-02-16 16:50:49 +01:00
|
|
|
printf("PCI: do_next_dev: unable to send to %d: %d\n",
|
2005-12-02 15:45:10 +01:00
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void do_find_dev(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, devind;
|
|
|
|
|
u8_t bus, dev, func;
|
|
|
|
|
|
|
|
|
|
bus= mp->m1_i1;
|
|
|
|
|
dev= mp->m1_i2;
|
|
|
|
|
func= mp->m1_i3;
|
|
|
|
|
|
|
|
|
|
r= pci_find_dev(bus, dev, func, &devind);
|
|
|
|
|
if (r == 1)
|
|
|
|
|
mp->m1_i1= devind;
|
|
|
|
|
mp->m_type= r;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
2007-02-16 16:50:49 +01:00
|
|
|
printf("PCI: do_find_dev: unable to send to %d: %d\n",
|
2005-12-02 15:45:10 +01:00
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void do_ids(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, devind;
|
|
|
|
|
u16_t vid, did;
|
|
|
|
|
|
|
|
|
|
devind= mp->m1_i1;
|
|
|
|
|
|
2008-02-22 16:56:12 +01:00
|
|
|
r= pci_ids_s(devind, &vid, &did);
|
|
|
|
|
if (r != OK)
|
|
|
|
|
{
|
|
|
|
|
printf("pci:do_ids: failed for devind %d: %d\n",
|
|
|
|
|
devind, r);
|
|
|
|
|
}
|
|
|
|
|
|
2005-12-02 15:45:10 +01:00
|
|
|
mp->m1_i1= vid;
|
|
|
|
|
mp->m1_i2= did;
|
2008-02-22 16:56:12 +01:00
|
|
|
mp->m_type= r;
|
2005-12-02 15:45:10 +01:00
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
2007-02-16 16:50:49 +01:00
|
|
|
printf("PCI: do_ids: unable to send to %d: %d\n",
|
2005-12-02 15:45:10 +01:00
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void do_dev_name(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, name_len, len;
|
|
|
|
|
u16_t vid, did;
|
|
|
|
|
char *name_ptr, *name;
|
|
|
|
|
|
|
|
|
|
vid= mp->m1_i1;
|
|
|
|
|
did= mp->m1_i2;
|
|
|
|
|
name_len= mp->m1_i3;
|
|
|
|
|
name_ptr= mp->m1_p1;
|
|
|
|
|
|
|
|
|
|
name= pci_dev_name(vid, did);
|
|
|
|
|
if (name == NULL)
|
|
|
|
|
{
|
|
|
|
|
/* No name */
|
|
|
|
|
r= ENOENT;
|
|
|
|
|
}
|
|
|
|
|
else
|
|
|
|
|
{
|
|
|
|
|
len= strlen(name)+1;
|
|
|
|
|
if (len > name_len)
|
|
|
|
|
len= name_len;
|
2007-02-16 16:50:49 +01:00
|
|
|
printf("PCI: pci`do_dev_name: calling do_vircopy\n");
|
2005-12-02 15:45:10 +01:00
|
|
|
r= sys_vircopy(SELF, D, (vir_bytes)name, mp->m_source, D,
|
|
|
|
|
(vir_bytes)name_ptr, len);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
mp->m_type= r;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
2007-02-16 16:50:49 +01:00
|
|
|
printf("PCI: do_dev_name: unable to send to %d: %d\n",
|
2005-12-02 15:45:10 +01:00
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2006-07-10 14:39:54 +02:00
|
|
|
PRIVATE void do_dev_name_s(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, name_len, len;
|
|
|
|
|
u16_t vid, did;
|
|
|
|
|
cp_grant_id_t name_gid;
|
|
|
|
|
char *name;
|
|
|
|
|
|
|
|
|
|
vid= mp->m7_i1;
|
|
|
|
|
did= mp->m7_i2;
|
|
|
|
|
name_len= mp->m7_i3;
|
|
|
|
|
name_gid= mp->m7_i4;
|
|
|
|
|
|
|
|
|
|
name= pci_dev_name(vid, did);
|
|
|
|
|
if (name == NULL)
|
|
|
|
|
{
|
|
|
|
|
/* No name */
|
|
|
|
|
r= ENOENT;
|
|
|
|
|
}
|
|
|
|
|
else
|
|
|
|
|
{
|
|
|
|
|
len= strlen(name)+1;
|
|
|
|
|
if (len > name_len)
|
|
|
|
|
len= name_len;
|
|
|
|
|
r= sys_safecopyto(mp->m_source, name_gid, 0, (vir_bytes)name,
|
|
|
|
|
len, D);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
mp->m_type= r;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
2007-02-16 16:50:49 +01:00
|
|
|
printf("PCI: do_dev_name: unable to send to %d: %d\n",
|
2006-07-10 14:39:54 +02:00
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void do_slot_name_s(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, devind, name_len, len;
|
|
|
|
|
cp_grant_id_t gid;
|
|
|
|
|
char *name;
|
|
|
|
|
|
|
|
|
|
devind= mp->m1_i1;
|
|
|
|
|
name_len= mp->m1_i2;
|
|
|
|
|
gid= mp->m1_i3;
|
|
|
|
|
|
2008-02-22 16:56:12 +01:00
|
|
|
r= pci_slot_name_s(devind, &name);
|
|
|
|
|
if (r != OK)
|
|
|
|
|
{
|
|
|
|
|
printf("pci:do_slot_name_s: failed for devind %d: %d\n",
|
|
|
|
|
devind, r);
|
|
|
|
|
}
|
2006-07-10 14:39:54 +02:00
|
|
|
|
2008-02-22 16:56:12 +01:00
|
|
|
if (r == OK)
|
|
|
|
|
{
|
|
|
|
|
len= strlen(name)+1;
|
|
|
|
|
if (len > name_len)
|
|
|
|
|
len= name_len;
|
|
|
|
|
r= sys_safecopyto(mp->m_source, gid, 0,
|
|
|
|
|
(vir_bytes)name, len, D);
|
|
|
|
|
}
|
2006-07-10 14:39:54 +02:00
|
|
|
|
|
|
|
|
mp->m_type= r;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
2007-02-16 16:50:49 +01:00
|
|
|
printf("PCI: do_slot_name: unable to send to %d: %d\n",
|
2006-07-10 14:39:54 +02:00
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2007-04-23 16:54:51 +02:00
|
|
|
PRIVATE void do_set_acl(mp)
|
2006-10-20 17:01:32 +02:00
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int i, r, gid;
|
|
|
|
|
|
|
|
|
|
if (mp->m_source != RS_PROC_NR)
|
|
|
|
|
{
|
2007-04-23 16:54:51 +02:00
|
|
|
printf("PCI: do_set_acl: not from RS\n");
|
2006-10-20 17:01:32 +02:00
|
|
|
reply(mp, EPERM);
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
for (i= 0; i<NR_DRIVERS; i++)
|
|
|
|
|
{
|
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
|
|
|
if (!pci_acl[i].inuse)
|
2006-10-20 17:01:32 +02:00
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
if (i >= NR_DRIVERS)
|
|
|
|
|
{
|
2007-04-23 16:54:51 +02:00
|
|
|
printf("PCI: do_set_acl: table is full\n");
|
2006-10-20 17:01:32 +02:00
|
|
|
reply(mp, ENOMEM);
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
gid= mp->m1_i1;
|
|
|
|
|
|
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
|
|
|
r= sys_safecopyfrom(mp->m_source, gid, 0, (vir_bytes)&pci_acl[i].acl,
|
|
|
|
|
sizeof(pci_acl[i].acl), D);
|
2006-10-20 17:01:32 +02:00
|
|
|
if (r != OK)
|
|
|
|
|
{
|
2007-04-23 16:54:51 +02:00
|
|
|
printf("PCI: do_set_acl: safecopyfrom failed\n");
|
2006-10-20 17:01:32 +02:00
|
|
|
reply(mp, r);
|
|
|
|
|
return;
|
|
|
|
|
}
|
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
|
|
|
pci_acl[i].inuse= 1;
|
2009-08-27 09:10:03 +02:00
|
|
|
if(debug)
|
2007-02-16 16:50:49 +01:00
|
|
|
printf("PCI: do_acl: setting ACL for %d ('%s') at entry %d\n",
|
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
|
|
|
pci_acl[i].acl.rsp_endpoint, pci_acl[i].acl.rsp_label,
|
2006-10-20 17:01:32 +02:00
|
|
|
i);
|
|
|
|
|
|
|
|
|
|
reply(mp, OK);
|
|
|
|
|
}
|
|
|
|
|
|
2007-04-23 16:54:51 +02:00
|
|
|
PRIVATE void do_del_acl(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int i, r, proc_nr;
|
|
|
|
|
|
|
|
|
|
if (mp->m_source != RS_PROC_NR)
|
|
|
|
|
{
|
|
|
|
|
printf("do_del_acl: not from RS\n");
|
|
|
|
|
reply(mp, EPERM);
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
proc_nr= mp->m1_i1;
|
|
|
|
|
|
|
|
|
|
for (i= 0; i<NR_DRIVERS; i++)
|
|
|
|
|
{
|
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
|
|
|
if (!pci_acl[i].inuse)
|
2007-04-23 16:54:51 +02:00
|
|
|
continue;
|
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
|
|
|
if (pci_acl[i].acl.rsp_endpoint == proc_nr)
|
2007-04-23 16:54:51 +02:00
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (i >= NR_DRIVERS)
|
|
|
|
|
{
|
|
|
|
|
printf("do_del_acl: nothing found for %d\n", proc_nr);
|
|
|
|
|
reply(mp, EINVAL);
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
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
|
|
|
pci_acl[i].inuse= 0;
|
2008-11-19 13:26:10 +01:00
|
|
|
#if 0
|
2007-04-23 16:54:51 +02:00
|
|
|
printf("do_acl: deleting ACL for %d ('%s') at entry %d\n",
|
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
|
|
|
pci_acl[i].acl.rsp_endpoint, pci_acl[i].acl.rsp_label, i);
|
2008-11-19 13:26:10 +01:00
|
|
|
#endif
|
2007-04-23 16:54:51 +02:00
|
|
|
|
2007-04-24 14:55:37 +02:00
|
|
|
/* Also release all devices held by this process */
|
|
|
|
|
pci_release(proc_nr);
|
|
|
|
|
|
2007-04-23 16:54:51 +02:00
|
|
|
reply(mp, OK);
|
|
|
|
|
}
|
|
|
|
|
|
2005-12-02 15:45:10 +01:00
|
|
|
PRIVATE void do_reserve(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
2006-01-12 15:46:12 +01:00
|
|
|
int i, r, devind;
|
|
|
|
|
|
2005-12-02 15:45:10 +01:00
|
|
|
devind= mp->m1_i1;
|
2007-02-20 18:09:19 +01:00
|
|
|
|
2007-04-24 14:55:37 +02:00
|
|
|
mp->m_type= pci_reserve2(devind, mp->m_source);
|
2005-12-02 15:45:10 +01:00
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
|
|
|
|
printf("do_reserve: unable to send to %d: %d\n",
|
|
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void do_attr_r8(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, devind, port;
|
|
|
|
|
u8_t v;
|
|
|
|
|
|
|
|
|
|
devind= mp->m2_i1;
|
|
|
|
|
port= mp->m2_i2;
|
|
|
|
|
|
2008-02-22 16:56:12 +01:00
|
|
|
r= pci_attr_r8_s(devind, port, &v);
|
|
|
|
|
if (r != OK)
|
|
|
|
|
{
|
|
|
|
|
printf(
|
|
|
|
|
"pci:do_attr_r8: pci_attr_r8_s(%d, %d, ...) failed: %d\n",
|
|
|
|
|
devind, port, r);
|
|
|
|
|
}
|
2005-12-02 15:45:10 +01:00
|
|
|
mp->m2_l1= v;
|
2008-02-22 16:56:12 +01:00
|
|
|
mp->m_type= r;
|
2005-12-02 15:45:10 +01:00
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
|
|
|
|
printf("do_attr_r8: unable to send to %d: %d\n",
|
|
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2006-01-12 15:46:12 +01:00
|
|
|
PRIVATE void do_attr_r16(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, devind, port;
|
|
|
|
|
u32_t v;
|
|
|
|
|
|
|
|
|
|
devind= mp->m2_i1;
|
|
|
|
|
port= mp->m2_i2;
|
|
|
|
|
|
|
|
|
|
v= pci_attr_r16(devind, port);
|
|
|
|
|
mp->m2_l1= v;
|
|
|
|
|
mp->m_type= OK;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
|
|
|
|
printf("do_attr_r16: unable to send to %d: %d\n",
|
|
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2005-12-02 15:45:10 +01:00
|
|
|
PRIVATE void do_attr_r32(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, devind, port;
|
|
|
|
|
u32_t v;
|
|
|
|
|
|
|
|
|
|
devind= mp->m2_i1;
|
|
|
|
|
port= mp->m2_i2;
|
|
|
|
|
|
2008-02-22 16:56:12 +01:00
|
|
|
r= pci_attr_r32_s(devind, port, &v);
|
|
|
|
|
if (r != OK)
|
|
|
|
|
{
|
|
|
|
|
printf(
|
|
|
|
|
"pci:do_attr_r32: pci_attr_r32_s(%d, %d, ...) failed: %d\n",
|
|
|
|
|
devind, port, r);
|
|
|
|
|
}
|
2005-12-02 15:45:10 +01:00
|
|
|
mp->m2_l1= v;
|
|
|
|
|
mp->m_type= OK;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
|
|
|
|
printf("do_attr_r32: unable to send to %d: %d\n",
|
|
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2006-01-12 15:46:12 +01:00
|
|
|
PRIVATE void do_attr_w8(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, devind, port;
|
|
|
|
|
u8_t v;
|
|
|
|
|
|
|
|
|
|
devind= mp->m2_i1;
|
|
|
|
|
port= mp->m2_i2;
|
|
|
|
|
v= mp->m2_l1;
|
|
|
|
|
|
|
|
|
|
pci_attr_w8(devind, port, v);
|
|
|
|
|
mp->m_type= OK;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
|
|
|
|
printf("do_attr_w8: unable to send to %d: %d\n",
|
|
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
PRIVATE void do_attr_w16(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, devind, port;
|
|
|
|
|
u16_t v;
|
|
|
|
|
|
|
|
|
|
devind= mp->m2_i1;
|
|
|
|
|
port= mp->m2_i2;
|
|
|
|
|
v= mp->m2_l1;
|
|
|
|
|
|
|
|
|
|
pci_attr_w16(devind, port, v);
|
|
|
|
|
mp->m_type= OK;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
|
|
|
|
printf("do_attr_w16: unable to send to %d: %d\n",
|
|
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2005-12-02 15:45:10 +01:00
|
|
|
PRIVATE void do_attr_w32(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, devind, port;
|
|
|
|
|
u32_t v;
|
|
|
|
|
|
|
|
|
|
devind= mp->m2_i1;
|
|
|
|
|
port= mp->m2_i2;
|
|
|
|
|
v= mp->m2_l1;
|
|
|
|
|
|
|
|
|
|
pci_attr_w32(devind, port, v);
|
|
|
|
|
mp->m_type= OK;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
|
|
|
|
printf("do_attr_w32: unable to send to %d: %d\n",
|
|
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2006-01-12 15:46:12 +01:00
|
|
|
PRIVATE void do_rescan_bus(mp)
|
|
|
|
|
message *mp;
|
|
|
|
|
{
|
|
|
|
|
int r, busnr;
|
|
|
|
|
|
|
|
|
|
busnr= mp->m2_i1;
|
|
|
|
|
|
|
|
|
|
pci_rescan_bus(busnr);
|
|
|
|
|
mp->m_type= OK;
|
|
|
|
|
r= send(mp->m_source, mp);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
{
|
|
|
|
|
printf("do_rescan_bus: unable to send to %d: %d\n",
|
|
|
|
|
mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2006-10-20 17:01:32 +02:00
|
|
|
|
|
|
|
|
PRIVATE void reply(mp, result)
|
|
|
|
|
message *mp;
|
|
|
|
|
int result;
|
|
|
|
|
{
|
|
|
|
|
int r;
|
|
|
|
|
message m;
|
|
|
|
|
|
|
|
|
|
m.m_type= result;
|
|
|
|
|
r= send(mp->m_source, &m);
|
|
|
|
|
if (r != 0)
|
|
|
|
|
printf("reply: unable to send to %d: %d\n", mp->m_source, r);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PRIVATE struct rs_pci *find_acl(endpoint)
|
|
|
|
|
int endpoint;
|
|
|
|
|
{
|
|
|
|
|
int i;
|
|
|
|
|
|
|
|
|
|
/* Find ACL entry for caller */
|
|
|
|
|
for (i= 0; i<NR_DRIVERS; i++)
|
|
|
|
|
{
|
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
|
|
|
if (!pci_acl[i].inuse)
|
2006-10-20 17:01:32 +02:00
|
|
|
continue;
|
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
|
|
|
if (pci_acl[i].acl.rsp_endpoint == endpoint)
|
|
|
|
|
return &pci_acl[i].acl;
|
2006-10-20 17:01:32 +02:00
|
|
|
}
|
|
|
|
|
return NULL;
|
|
|
|
|
}
|
