2005-04-21 16:53:53 +02:00
|
|
|
/* This file contains the printer driver. It is a fairly simple driver,
|
|
|
|
* supporting only one printer. Characters that are written to the driver
|
|
|
|
* are written to the printer without any changes at all.
|
|
|
|
*
|
|
|
|
* Changes:
|
2005-04-29 17:36:43 +02:00
|
|
|
* May 07, 2004 fix: wait until printer is ready (Jorrit N. Herder)
|
2005-04-21 16:53:53 +02:00
|
|
|
* May 06, 2004 printer driver moved to user-space (Jorrit N. Herder)
|
|
|
|
*
|
|
|
|
* The valid messages and their parameters are:
|
|
|
|
*
|
|
|
|
* DEV_OPEN: initializes the printer
|
|
|
|
* DEV_CLOSE: does nothing
|
|
|
|
* HARD_INT: interrupt handler has finished current chunk of output
|
|
|
|
* DEV_WRITE: a process wants to write on a terminal
|
2005-06-24 18:21:54 +02:00
|
|
|
* CANCEL: terminate a previous incomplete system call immediately
|
2005-04-21 16:53:53 +02:00
|
|
|
*
|
Server/driver protocols: no longer allow third-party copies.
Before safecopies, the IO_ENDPT and DL_ENDPT message fields were needed
to know which actual process to copy data from/to, as that process may
not always be the caller. Now that we have full safecopy support, these
fields have become useless for that purpose: the owner of the grant is
*always* the caller. Allowing the caller to supply another endpoint is
in fact dangerous, because the callee may then end up using a grant
from a third party. One could call this a variant of the confused
deputy problem.
From now on, safecopy calls should always use the caller's endpoint as
grant owner. This fully obsoletes the DL_ENDPT field in the
inet/ethernet protocol. IO_ENDPT has other uses besides identifying the
grant owner though. This patch renames IO_ENDPT to USER_ENDPT, not only
because that is a more fitting name (it should never be used for I/O
after all), but also in order to intentionally break any old system
source code outside the base system. If this patch breaks your code,
fixing it is fairly simple:
- DL_ENDPT should be replaced with m_source;
- IO_ENDPT should be replaced with m_source when used for safecopies;
- IO_ENDPT should be replaced with USER_ENDPT for any other use, e.g.
when setting REP_ENDPT, matching requests in CANCEL calls, getting
DEV_SELECT flags, and retrieving of the real user process's endpoint
in DEV_OPEN.
The changes in this patch are binary backward compatible.
2011-04-11 19:35:05 +02:00
|
|
|
* m_type TTY_LINE USER_ENDPT COUNT ADDRESS
|
2005-04-21 16:53:53 +02:00
|
|
|
* |-------------+---------+---------+---------+---------|
|
|
|
|
* | DEV_OPEN | | | | |
|
|
|
|
* |-------------+---------+---------+---------+---------|
|
|
|
|
* | DEV_CLOSE | | proc nr | | |
|
|
|
|
* -------------------------------------------------------
|
|
|
|
* | HARD_INT | | | | |
|
|
|
|
* |-------------+---------+---------+---------+---------|
|
2005-07-26 14:50:25 +02:00
|
|
|
* | SYS_EVENT | | | | |
|
2005-04-21 16:53:53 +02:00
|
|
|
* |-------------+---------+---------+---------+---------|
|
|
|
|
* | DEV_WRITE |minor dev| proc nr | count | buf ptr |
|
|
|
|
* |-------------+---------+---------+---------+---------|
|
|
|
|
* | CANCEL |minor dev| proc nr | | |
|
|
|
|
* -------------------------------------------------------
|
|
|
|
*
|
|
|
|
* Note: since only 1 printer is supported, minor dev is not used at present.
|
|
|
|
*/
|
|
|
|
|
2009-09-29 20:47:56 +02:00
|
|
|
#include <minix/endpoint.h>
|
2010-03-22 22:25:22 +01:00
|
|
|
#include <minix/drivers.h>
|
Split block/character protocols and libdriver
This patch separates the character and block driver communication
protocols. The old character protocol remains the same, but a new
block protocol is introduced. The libdriver library is replaced by
two new libraries: libchardriver and libblockdriver. Their exposed
API, and drivers that use them, have been updated accordingly.
Together, libbdev and libblockdriver now completely abstract away
the message format used by the block protocol. As the memory driver
is both a character and a block device driver, it now implements its
own message loop.
The most important semantic change made to the block protocol is that
it is no longer possible to return both partial results and an error
for a single transfer. This simplifies the interaction between the
caller and the driver, as the I/O vector no longer needs to be copied
back. Also, drivers are now no longer supposed to decide based on the
layout of the I/O vector when a transfer should be cut short. Put
simply, transfers are now supposed to either succeed completely, or
result in an error.
After this patch, the state of the various pieces is as follows:
- block protocol: stable
- libbdev API: stable for synchronous communication
- libblockdriver API: needs slight revision (the drvlib/partition API
in particular; the threading API will also change shortly)
- character protocol: needs cleanup
- libchardriver API: needs cleanup accordingly
- driver restarts: largely unsupported until endpoint changes are
reintroduced
As a side effect, this patch eliminates several bugs, hacks, and gcc
-Wall and -W warnings all over the place. It probably introduces a
few new ones, too.
Update warning: this patch changes the protocol between MFS and disk
drivers, so in order to use old/new images, the MFS from the ramdisk
must be used to mount all file systems.
2011-11-22 13:27:53 +01:00
|
|
|
#include <minix/chardriver.h>
|
2005-04-21 16:53:53 +02:00
|
|
|
|
|
|
|
/* Control bits (in port_base + 2). "+" means positive logic and "-" means
|
|
|
|
* negative logic. Most of the signals are negative logic on the pins but
|
|
|
|
* many are converted to positive logic in the ports. Some manuals are
|
|
|
|
* misleading because they only document the pin logic.
|
|
|
|
*
|
|
|
|
* +0x01 Pin 1 -Strobe
|
|
|
|
* +0x02 Pin 14 -Auto Feed
|
|
|
|
* -0x04 Pin 16 -Initialize Printer
|
|
|
|
* +0x08 Pin 17 -Select Printer
|
|
|
|
* +0x10 IRQ7 Enable
|
|
|
|
*
|
|
|
|
* Auto Feed and Select Printer are always enabled. Strobe is enabled briefly
|
|
|
|
* when characters are output. Initialize Printer is enabled briefly when
|
|
|
|
* the task is started. IRQ7 is enabled when the first character is output
|
|
|
|
* and left enabled until output is completed (or later after certain
|
|
|
|
* abnormal completions).
|
|
|
|
*/
|
|
|
|
#define ASSERT_STROBE 0x1D /* strobe a character to the interface */
|
|
|
|
#define NEGATE_STROBE 0x1C /* enable interrupt on interface */
|
2005-06-06 13:40:32 +02:00
|
|
|
#define PR_SELECT 0x0C /* select printer bit */
|
2005-04-21 16:53:53 +02:00
|
|
|
#define INIT_PRINTER 0x08 /* init printer bits */
|
|
|
|
|
|
|
|
/* Status bits (in port_base + 2).
|
|
|
|
*
|
|
|
|
* -0x08 Pin 15 -Error
|
|
|
|
* +0x10 Pin 13 +Select Status
|
|
|
|
* +0x20 Pin 12 +Out of Paper
|
|
|
|
* -0x40 Pin 10 -Acknowledge
|
|
|
|
* -0x80 Pin 11 +Busy
|
|
|
|
*/
|
|
|
|
#define BUSY_STATUS 0x10 /* printer gives this status when busy */
|
|
|
|
#define NO_PAPER 0x20 /* status bit saying that paper is out */
|
|
|
|
#define NORMAL_STATUS 0x90 /* printer gives this status when idle */
|
|
|
|
#define ON_LINE 0x10 /* status bit saying that printer is online */
|
|
|
|
#define STATUS_MASK 0xB0 /* mask to filter out status bits */
|
|
|
|
|
|
|
|
#define MAX_ONLINE_RETRIES 120 /* about 60s: waits 0.5s after each retry */
|
|
|
|
|
|
|
|
/* Centronics interface timing that must be met by software (in microsec).
|
|
|
|
*
|
|
|
|
* Strobe length: 0.5u to 100u (not sure about the upper limit).
|
|
|
|
* Data set up: 0.5u before strobe.
|
|
|
|
* Data hold: 0.5u after strobe.
|
|
|
|
* Init pulse length: over 200u (not sure).
|
|
|
|
*
|
|
|
|
* The strobe length is about 50u with the code here and function calls for
|
|
|
|
* sys_outb() - not much to spare. The 0.5u minimums will not be violated
|
|
|
|
* with the sys_outb() messages exchanged.
|
|
|
|
*/
|
|
|
|
|
2012-03-25 20:25:53 +02:00
|
|
|
static endpoint_t caller; /* process to tell when printing done (FS) */
|
|
|
|
static int revive_pending; /* set to true if revive is pending */
|
|
|
|
static int revive_status; /* revive status */
|
|
|
|
static int done_status; /* status of last output completion */
|
|
|
|
static int oleft; /* bytes of output left in obuf */
|
|
|
|
static unsigned char obuf[128]; /* output buffer */
|
|
|
|
static unsigned const char *optr; /* ptr to next char in obuf to print */
|
|
|
|
static int orig_count; /* original byte count */
|
|
|
|
static int port_base; /* I/O port for printer */
|
|
|
|
static endpoint_t proc_nr; /* user requesting the printing */
|
|
|
|
static cp_grant_id_t grant_nr; /* grant on which print happens */
|
|
|
|
static int user_left; /* bytes of output left in user buf */
|
|
|
|
static vir_bytes user_vir_d; /* offset in user buf */
|
|
|
|
int writing; /* nonzero while write is in progress */
|
|
|
|
static int irq_hook_id; /* id of irq hook at kernel */
|
|
|
|
|
|
|
|
static void do_cancel(message *m_ptr);
|
|
|
|
static void output_done(void);
|
|
|
|
static void do_write(message *m_ptr);
|
|
|
|
static void do_status(message *m_ptr);
|
|
|
|
static void prepare_output(void);
|
|
|
|
static int do_probe(void);
|
|
|
|
static void do_initialize(void);
|
|
|
|
static void reply(int code,int replyee,int proc,int status);
|
|
|
|
static void do_printer_output(void);
|
2005-06-24 18:21:54 +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 functions and variables. */
|
2012-03-25 20:25:53 +02:00
|
|
|
static void sef_local_startup(void);
|
|
|
|
static int sef_cb_init_fresh(int type, sef_init_info_t *info);
|
2012-03-24 16:16:34 +01:00
|
|
|
EXTERN int sef_cb_lu_prepare(int state);
|
|
|
|
EXTERN int sef_cb_lu_state_isvalid(int state);
|
|
|
|
EXTERN void sef_cb_lu_state_dump(int state);
|
2012-03-25 20:25:53 +02:00
|
|
|
int is_status_msg_expected = FALSE;
|
2005-06-24 18:21:54 +02:00
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* printer_task *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
int main(void)
|
2005-04-21 16:53:53 +02:00
|
|
|
{
|
|
|
|
/* Main routine of the printer task. */
|
|
|
|
message pr_mess; /* buffer for all incoming messages */
|
2010-04-08 15:41:35 +02:00
|
|
|
int ipc_status;
|
2005-10-12 17:06:00 +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. */
|
|
|
|
sef_local_startup();
|
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
while (TRUE) {
|
2010-04-08 15:41:35 +02:00
|
|
|
if(driver_receive(ANY, &pr_mess, &ipc_status) != OK) {
|
|
|
|
panic("driver_receive failed");
|
|
|
|
}
|
2009-09-29 20:47:56 +02:00
|
|
|
|
2010-04-08 15:41:35 +02:00
|
|
|
if (is_ipc_notify(ipc_status)) {
|
2009-09-29 20:47:56 +02:00
|
|
|
switch (_ENDPOINT_P(pr_mess.m_source)) {
|
|
|
|
case HARDWARE:
|
|
|
|
do_printer_output();
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
reply(TASK_REPLY, pr_mess.m_source,
|
Server/driver protocols: no longer allow third-party copies.
Before safecopies, the IO_ENDPT and DL_ENDPT message fields were needed
to know which actual process to copy data from/to, as that process may
not always be the caller. Now that we have full safecopy support, these
fields have become useless for that purpose: the owner of the grant is
*always* the caller. Allowing the caller to supply another endpoint is
in fact dangerous, because the callee may then end up using a grant
from a third party. One could call this a variant of the confused
deputy problem.
From now on, safecopy calls should always use the caller's endpoint as
grant owner. This fully obsoletes the DL_ENDPT field in the
inet/ethernet protocol. IO_ENDPT has other uses besides identifying the
grant owner though. This patch renames IO_ENDPT to USER_ENDPT, not only
because that is a more fitting name (it should never be used for I/O
after all), but also in order to intentionally break any old system
source code outside the base system. If this patch breaks your code,
fixing it is fairly simple:
- DL_ENDPT should be replaced with m_source;
- IO_ENDPT should be replaced with m_source when used for safecopies;
- IO_ENDPT should be replaced with USER_ENDPT for any other use, e.g.
when setting REP_ENDPT, matching requests in CANCEL calls, getting
DEV_SELECT flags, and retrieving of the real user process's endpoint
in DEV_OPEN.
The changes in this patch are binary backward compatible.
2011-04-11 19:35:05 +02:00
|
|
|
pr_mess.USER_ENDPT, EINVAL);
|
2009-09-29 20:47:56 +02:00
|
|
|
}
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
switch(pr_mess.m_type) {
|
|
|
|
case DEV_OPEN:
|
|
|
|
do_initialize(); /* initialize */
|
|
|
|
/* fall through */
|
|
|
|
case DEV_CLOSE:
|
Server/driver protocols: no longer allow third-party copies.
Before safecopies, the IO_ENDPT and DL_ENDPT message fields were needed
to know which actual process to copy data from/to, as that process may
not always be the caller. Now that we have full safecopy support, these
fields have become useless for that purpose: the owner of the grant is
*always* the caller. Allowing the caller to supply another endpoint is
in fact dangerous, because the callee may then end up using a grant
from a third party. One could call this a variant of the confused
deputy problem.
From now on, safecopy calls should always use the caller's endpoint as
grant owner. This fully obsoletes the DL_ENDPT field in the
inet/ethernet protocol. IO_ENDPT has other uses besides identifying the
grant owner though. This patch renames IO_ENDPT to USER_ENDPT, not only
because that is a more fitting name (it should never be used for I/O
after all), but also in order to intentionally break any old system
source code outside the base system. If this patch breaks your code,
fixing it is fairly simple:
- DL_ENDPT should be replaced with m_source;
- IO_ENDPT should be replaced with m_source when used for safecopies;
- IO_ENDPT should be replaced with USER_ENDPT for any other use, e.g.
when setting REP_ENDPT, matching requests in CANCEL calls, getting
DEV_SELECT flags, and retrieving of the real user process's endpoint
in DEV_OPEN.
The changes in this patch are binary backward compatible.
2011-04-11 19:35:05 +02:00
|
|
|
reply(TASK_REPLY, pr_mess.m_source, pr_mess.USER_ENDPT, OK);
|
2005-04-21 16:53:53 +02:00
|
|
|
break;
|
2011-03-25 11:45:57 +01:00
|
|
|
case DEV_WRITE_S: do_write(&pr_mess); break;
|
2005-07-27 17:04:30 +02:00
|
|
|
case DEV_STATUS: do_status(&pr_mess); break;
|
2005-08-05 20:57:20 +02:00
|
|
|
case CANCEL: do_cancel(&pr_mess); break;
|
2005-04-21 16:53:53 +02:00
|
|
|
default:
|
Server/driver protocols: no longer allow third-party copies.
Before safecopies, the IO_ENDPT and DL_ENDPT message fields were needed
to know which actual process to copy data from/to, as that process may
not always be the caller. Now that we have full safecopy support, these
fields have become useless for that purpose: the owner of the grant is
*always* the caller. Allowing the caller to supply another endpoint is
in fact dangerous, because the callee may then end up using a grant
from a third party. One could call this a variant of the confused
deputy problem.
From now on, safecopy calls should always use the caller's endpoint as
grant owner. This fully obsoletes the DL_ENDPT field in the
inet/ethernet protocol. IO_ENDPT has other uses besides identifying the
grant owner though. This patch renames IO_ENDPT to USER_ENDPT, not only
because that is a more fitting name (it should never be used for I/O
after all), but also in order to intentionally break any old system
source code outside the base system. If this patch breaks your code,
fixing it is fairly simple:
- DL_ENDPT should be replaced with m_source;
- IO_ENDPT should be replaced with m_source when used for safecopies;
- IO_ENDPT should be replaced with USER_ENDPT for any other use, e.g.
when setting REP_ENDPT, matching requests in CANCEL calls, getting
DEV_SELECT flags, and retrieving of the real user process's endpoint
in DEV_OPEN.
The changes in this patch are binary backward compatible.
2011-04-11 19:35:05 +02:00
|
|
|
reply(TASK_REPLY, pr_mess.m_source, pr_mess.USER_ENDPT,
|
|
|
|
EINVAL);
|
2005-04-21 16:53:53 +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 *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void sef_local_startup()
|
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
|
|
|
{
|
2010-04-08 15:41:35 +02: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);
|
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
|
|
|
|
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);
|
|
|
|
sef_setcb_lu_state_isvalid(sef_cb_lu_state_isvalid);
|
|
|
|
sef_setcb_lu_state_dump(sef_cb_lu_state_dump);
|
|
|
|
|
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
|
|
|
/* Register signal callbacks. */
|
|
|
|
sef_setcb_signal_handler(sef_cb_signal_handler_term);
|
|
|
|
|
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
|
|
|
/* Let SEF perform startup. */
|
|
|
|
sef_startup();
|
|
|
|
}
|
2005-10-12 17:06:00 +02:00
|
|
|
|
2010-04-08 15:41:35 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* sef_cb_init_fresh *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static int sef_cb_init_fresh(int UNUSED(type), sef_init_info_t *UNUSED(info))
|
2010-04-08 15:41:35 +02:00
|
|
|
{
|
|
|
|
/* Initialize the printer driver. */
|
2011-12-05 10:54:58 +01:00
|
|
|
|
|
|
|
/* If no printer is present, do not start. */
|
|
|
|
if (!do_probe())
|
|
|
|
return ENODEV; /* arbitrary error code */
|
|
|
|
|
2010-04-08 15:41:35 +02:00
|
|
|
/* Announce we are up! */
|
Split block/character protocols and libdriver
This patch separates the character and block driver communication
protocols. The old character protocol remains the same, but a new
block protocol is introduced. The libdriver library is replaced by
two new libraries: libchardriver and libblockdriver. Their exposed
API, and drivers that use them, have been updated accordingly.
Together, libbdev and libblockdriver now completely abstract away
the message format used by the block protocol. As the memory driver
is both a character and a block device driver, it now implements its
own message loop.
The most important semantic change made to the block protocol is that
it is no longer possible to return both partial results and an error
for a single transfer. This simplifies the interaction between the
caller and the driver, as the I/O vector no longer needs to be copied
back. Also, drivers are now no longer supposed to decide based on the
layout of the I/O vector when a transfer should be cut short. Put
simply, transfers are now supposed to either succeed completely, or
result in an error.
After this patch, the state of the various pieces is as follows:
- block protocol: stable
- libbdev API: stable for synchronous communication
- libblockdriver API: needs slight revision (the drvlib/partition API
in particular; the threading API will also change shortly)
- character protocol: needs cleanup
- libchardriver API: needs cleanup accordingly
- driver restarts: largely unsupported until endpoint changes are
reintroduced
As a side effect, this patch eliminates several bugs, hacks, and gcc
-Wall and -W warnings all over the place. It probably introduces a
few new ones, too.
Update warning: this patch changes the protocol between MFS and disk
drivers, so in order to use old/new images, the MFS from the ramdisk
must be used to mount all file systems.
2011-11-22 13:27:53 +01:00
|
|
|
chardriver_announce();
|
2010-04-08 15:41:35 +02:00
|
|
|
|
|
|
|
return OK;
|
|
|
|
}
|
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* do_write *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void do_write(m_ptr)
|
2005-04-21 16:53:53 +02:00
|
|
|
register message *m_ptr; /* pointer to the newly arrived message */
|
|
|
|
{
|
|
|
|
/* The printer is used by sending DEV_WRITE messages to it. Process one. */
|
|
|
|
|
|
|
|
register int r = SUSPEND;
|
|
|
|
int retries;
|
2012-03-05 00:11:41 +01:00
|
|
|
u32_t status;
|
2005-04-21 16:53:53 +02:00
|
|
|
|
|
|
|
/* Reject command if last write is not yet finished, the count is not
|
|
|
|
* positive, or the user address is bad.
|
|
|
|
*/
|
2013-08-30 10:48:34 +02:00
|
|
|
if (writing) r = EIO;
|
|
|
|
else if (m_ptr->COUNT <= 0) r = EINVAL;
|
|
|
|
else if (m_ptr->FLAGS & FLG_OP_NONBLOCK) r = EAGAIN; /* not supported */
|
2005-04-21 16:53:53 +02:00
|
|
|
|
|
|
|
/* Reply to FS, no matter what happened, possible SUSPEND caller. */
|
Server/driver protocols: no longer allow third-party copies.
Before safecopies, the IO_ENDPT and DL_ENDPT message fields were needed
to know which actual process to copy data from/to, as that process may
not always be the caller. Now that we have full safecopy support, these
fields have become useless for that purpose: the owner of the grant is
*always* the caller. Allowing the caller to supply another endpoint is
in fact dangerous, because the callee may then end up using a grant
from a third party. One could call this a variant of the confused
deputy problem.
From now on, safecopy calls should always use the caller's endpoint as
grant owner. This fully obsoletes the DL_ENDPT field in the
inet/ethernet protocol. IO_ENDPT has other uses besides identifying the
grant owner though. This patch renames IO_ENDPT to USER_ENDPT, not only
because that is a more fitting name (it should never be used for I/O
after all), but also in order to intentionally break any old system
source code outside the base system. If this patch breaks your code,
fixing it is fairly simple:
- DL_ENDPT should be replaced with m_source;
- IO_ENDPT should be replaced with m_source when used for safecopies;
- IO_ENDPT should be replaced with USER_ENDPT for any other use, e.g.
when setting REP_ENDPT, matching requests in CANCEL calls, getting
DEV_SELECT flags, and retrieving of the real user process's endpoint
in DEV_OPEN.
The changes in this patch are binary backward compatible.
2011-04-11 19:35:05 +02:00
|
|
|
reply(TASK_REPLY, m_ptr->m_source, m_ptr->USER_ENDPT, r);
|
2005-04-21 16:53:53 +02:00
|
|
|
|
|
|
|
/* If no errors occurred, continue printing with SUSPENDED caller.
|
|
|
|
* First wait until the printer is online to prevent stupid errors.
|
|
|
|
*/
|
|
|
|
if (SUSPEND == r) {
|
|
|
|
caller = m_ptr->m_source;
|
Server/driver protocols: no longer allow third-party copies.
Before safecopies, the IO_ENDPT and DL_ENDPT message fields were needed
to know which actual process to copy data from/to, as that process may
not always be the caller. Now that we have full safecopy support, these
fields have become useless for that purpose: the owner of the grant is
*always* the caller. Allowing the caller to supply another endpoint is
in fact dangerous, because the callee may then end up using a grant
from a third party. One could call this a variant of the confused
deputy problem.
From now on, safecopy calls should always use the caller's endpoint as
grant owner. This fully obsoletes the DL_ENDPT field in the
inet/ethernet protocol. IO_ENDPT has other uses besides identifying the
grant owner though. This patch renames IO_ENDPT to USER_ENDPT, not only
because that is a more fitting name (it should never be used for I/O
after all), but also in order to intentionally break any old system
source code outside the base system. If this patch breaks your code,
fixing it is fairly simple:
- DL_ENDPT should be replaced with m_source;
- IO_ENDPT should be replaced with m_source when used for safecopies;
- IO_ENDPT should be replaced with USER_ENDPT for any other use, e.g.
when setting REP_ENDPT, matching requests in CANCEL calls, getting
DEV_SELECT flags, and retrieving of the real user process's endpoint
in DEV_OPEN.
The changes in this patch are binary backward compatible.
2011-04-11 19:35:05 +02:00
|
|
|
proc_nr = m_ptr->USER_ENDPT;
|
2005-04-21 16:53:53 +02:00
|
|
|
user_left = m_ptr->COUNT;
|
|
|
|
orig_count = m_ptr->COUNT;
|
2011-03-25 11:45:57 +01:00
|
|
|
user_vir_d = 0; /* Offset. */
|
2005-04-21 16:53:53 +02:00
|
|
|
writing = TRUE;
|
2011-03-25 11:45:57 +01:00
|
|
|
grant_nr = (cp_grant_id_t) m_ptr->IO_GRANT;
|
2005-04-21 16:53:53 +02:00
|
|
|
|
|
|
|
retries = MAX_ONLINE_RETRIES + 1;
|
|
|
|
while (--retries > 0) {
|
2007-08-06 13:17:08 +02:00
|
|
|
if(sys_inb(port_base + 1, &status) != OK) {
|
|
|
|
printf("printer: sys_inb of %x failed\n", port_base+1);
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("sys_inb failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
2005-04-21 16:53:53 +02:00
|
|
|
if ((status & ON_LINE)) { /* printer online! */
|
|
|
|
prepare_output();
|
|
|
|
do_printer_output();
|
|
|
|
return;
|
|
|
|
}
|
2008-12-11 15:42:23 +01:00
|
|
|
micro_delay(500000); /* wait before retry */
|
2005-04-21 16:53:53 +02:00
|
|
|
}
|
|
|
|
/* If we reach this point, the printer was not online in time. */
|
|
|
|
done_status = status;
|
|
|
|
output_done();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
2005-10-12 17:06:00 +02:00
|
|
|
* output_done *
|
2005-04-21 16:53:53 +02:00
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void output_done()
|
2005-04-21 16:53:53 +02:00
|
|
|
{
|
|
|
|
/* Previous chunk of printing is finished. Continue if OK and more.
|
|
|
|
* Otherwise, reply to caller (FS).
|
|
|
|
*/
|
|
|
|
register int status;
|
|
|
|
|
|
|
|
if (!writing) return; /* probably leftover interrupt */
|
|
|
|
if (done_status != OK) { /* printer error occurred */
|
|
|
|
status = EIO;
|
|
|
|
if ((done_status & ON_LINE) == 0) {
|
|
|
|
printf("Printer is not on line\n");
|
|
|
|
} else if ((done_status & NO_PAPER)) {
|
|
|
|
printf("Printer is out of paper\n");
|
|
|
|
status = EAGAIN;
|
|
|
|
} else {
|
|
|
|
printf("Printer error, status is 0x%02X\n", done_status);
|
|
|
|
}
|
|
|
|
/* Some characters have been printed, tell how many. */
|
|
|
|
if (status == EAGAIN && user_left < orig_count) {
|
|
|
|
status = orig_count - user_left;
|
|
|
|
}
|
|
|
|
oleft = 0; /* cancel further output */
|
|
|
|
}
|
|
|
|
else if (user_left != 0) { /* not yet done, continue! */
|
|
|
|
prepare_output();
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
else { /* done! report back to FS */
|
|
|
|
status = orig_count;
|
|
|
|
}
|
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
|
|
|
is_status_msg_expected = TRUE;
|
2005-07-27 17:04:30 +02:00
|
|
|
revive_pending = TRUE;
|
|
|
|
revive_status = status;
|
2005-07-29 17:00:22 +02:00
|
|
|
notify(caller);
|
2005-04-21 16:53:53 +02:00
|
|
|
}
|
|
|
|
|
2005-07-27 17:04:30 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* do_status *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void do_status(m_ptr)
|
2005-07-27 17:04:30 +02:00
|
|
|
register message *m_ptr; /* pointer to the newly arrived message */
|
|
|
|
{
|
|
|
|
if (revive_pending) {
|
|
|
|
m_ptr->m_type = DEV_REVIVE; /* build message */
|
2006-03-03 11:21:45 +01:00
|
|
|
m_ptr->REP_ENDPT = proc_nr;
|
2005-07-27 17:04:30 +02:00
|
|
|
m_ptr->REP_STATUS = revive_status;
|
2006-06-20 11:49:02 +02:00
|
|
|
m_ptr->REP_IO_GRANT = grant_nr;
|
2005-07-27 17:04:30 +02:00
|
|
|
|
|
|
|
writing = FALSE; /* unmark event */
|
|
|
|
revive_pending = FALSE; /* unmark event */
|
|
|
|
} else {
|
|
|
|
m_ptr->m_type = DEV_NO_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
|
|
|
|
|
|
|
is_status_msg_expected = FALSE;
|
2005-07-27 17:04:30 +02:00
|
|
|
}
|
|
|
|
send(m_ptr->m_source, m_ptr); /* send the message */
|
|
|
|
}
|
2005-04-21 16:53:53 +02:00
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* do_cancel *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void do_cancel(m_ptr)
|
2005-04-21 16:53:53 +02:00
|
|
|
register message *m_ptr; /* pointer to the newly arrived message */
|
|
|
|
{
|
|
|
|
/* Cancel a print request that has already started. Usually this means that
|
|
|
|
* the process doing the printing has been killed by a signal. It is not
|
|
|
|
* clear if there are race conditions. Try not to cancel the wrong process,
|
|
|
|
* but rely on FS to handle the EINTR reply and de-suspension properly.
|
|
|
|
*/
|
|
|
|
|
Server/driver protocols: no longer allow third-party copies.
Before safecopies, the IO_ENDPT and DL_ENDPT message fields were needed
to know which actual process to copy data from/to, as that process may
not always be the caller. Now that we have full safecopy support, these
fields have become useless for that purpose: the owner of the grant is
*always* the caller. Allowing the caller to supply another endpoint is
in fact dangerous, because the callee may then end up using a grant
from a third party. One could call this a variant of the confused
deputy problem.
From now on, safecopy calls should always use the caller's endpoint as
grant owner. This fully obsoletes the DL_ENDPT field in the
inet/ethernet protocol. IO_ENDPT has other uses besides identifying the
grant owner though. This patch renames IO_ENDPT to USER_ENDPT, not only
because that is a more fitting name (it should never be used for I/O
after all), but also in order to intentionally break any old system
source code outside the base system. If this patch breaks your code,
fixing it is fairly simple:
- DL_ENDPT should be replaced with m_source;
- IO_ENDPT should be replaced with m_source when used for safecopies;
- IO_ENDPT should be replaced with USER_ENDPT for any other use, e.g.
when setting REP_ENDPT, matching requests in CANCEL calls, getting
DEV_SELECT flags, and retrieving of the real user process's endpoint
in DEV_OPEN.
The changes in this patch are binary backward compatible.
2011-04-11 19:35:05 +02:00
|
|
|
if (writing && m_ptr->USER_ENDPT == proc_nr) {
|
2005-04-21 16:53:53 +02:00
|
|
|
oleft = 0; /* cancel output by interrupt handler */
|
|
|
|
writing = FALSE;
|
2005-07-27 17:04:30 +02:00
|
|
|
revive_pending = FALSE;
|
2005-04-21 16:53:53 +02:00
|
|
|
}
|
Server/driver protocols: no longer allow third-party copies.
Before safecopies, the IO_ENDPT and DL_ENDPT message fields were needed
to know which actual process to copy data from/to, as that process may
not always be the caller. Now that we have full safecopy support, these
fields have become useless for that purpose: the owner of the grant is
*always* the caller. Allowing the caller to supply another endpoint is
in fact dangerous, because the callee may then end up using a grant
from a third party. One could call this a variant of the confused
deputy problem.
From now on, safecopy calls should always use the caller's endpoint as
grant owner. This fully obsoletes the DL_ENDPT field in the
inet/ethernet protocol. IO_ENDPT has other uses besides identifying the
grant owner though. This patch renames IO_ENDPT to USER_ENDPT, not only
because that is a more fitting name (it should never be used for I/O
after all), but also in order to intentionally break any old system
source code outside the base system. If this patch breaks your code,
fixing it is fairly simple:
- DL_ENDPT should be replaced with m_source;
- IO_ENDPT should be replaced with m_source when used for safecopies;
- IO_ENDPT should be replaced with USER_ENDPT for any other use, e.g.
when setting REP_ENDPT, matching requests in CANCEL calls, getting
DEV_SELECT flags, and retrieving of the real user process's endpoint
in DEV_OPEN.
The changes in this patch are binary backward compatible.
2011-04-11 19:35:05 +02:00
|
|
|
reply(TASK_REPLY, m_ptr->m_source, m_ptr->USER_ENDPT, EINTR);
|
2005-04-21 16:53:53 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* reply *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void reply(code, replyee, process, status)
|
2005-04-21 16:53:53 +02:00
|
|
|
int code; /* TASK_REPLY or REVIVE */
|
|
|
|
int replyee; /* destination for message (normally FS) */
|
|
|
|
int process; /* which user requested the printing */
|
|
|
|
int status; /* number of chars printed or error code */
|
|
|
|
{
|
|
|
|
/* Send a reply telling FS that printing has started or stopped. */
|
|
|
|
|
|
|
|
message pr_mess;
|
|
|
|
|
|
|
|
pr_mess.m_type = code; /* TASK_REPLY or REVIVE */
|
|
|
|
pr_mess.REP_STATUS = status; /* count or EIO */
|
2006-03-03 11:21:45 +01:00
|
|
|
pr_mess.REP_ENDPT = process; /* which user does this pertain to */
|
2005-04-21 16:53:53 +02:00
|
|
|
send(replyee, &pr_mess); /* send the message */
|
|
|
|
}
|
|
|
|
|
2011-12-05 10:54:58 +01:00
|
|
|
/*===========================================================================*
|
|
|
|
* do_probe *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static int do_probe(void)
|
2011-12-05 10:54:58 +01:00
|
|
|
{
|
|
|
|
/* See if there is a printer at all. */
|
|
|
|
|
|
|
|
/* Get the base port for first printer. */
|
2012-05-09 18:34:40 +02:00
|
|
|
if(sys_readbios(LPT1_IO_PORT_ADDR, &port_base, LPT1_IO_PORT_SIZE) != OK) {
|
|
|
|
panic("do_initialize: sys_readbios failed");
|
2011-12-05 10:54:58 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/* If the port is zero, the parallel port is not available at all. */
|
|
|
|
return (port_base != 0);
|
|
|
|
}
|
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
/*===========================================================================*
|
|
|
|
* do_initialize *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void do_initialize()
|
2005-04-21 16:53:53 +02:00
|
|
|
{
|
|
|
|
/* Set global variables and initialize the printer. */
|
|
|
|
static int initialized = FALSE;
|
|
|
|
if (initialized) return;
|
|
|
|
initialized = TRUE;
|
|
|
|
|
2007-08-06 13:17:08 +02:00
|
|
|
if(sys_outb(port_base + 2, INIT_PRINTER) != OK) {
|
|
|
|
printf("printer: sys_outb of %x failed\n", port_base+2);
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("do_initialize: sys_outb init failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
2008-12-11 15:42:23 +01:00
|
|
|
micro_delay(1000000/20); /* easily satisfies Centronics minimum */
|
2007-08-06 13:17:08 +02:00
|
|
|
if(sys_outb(port_base + 2, PR_SELECT) != OK) {
|
|
|
|
printf("printer: sys_outb of %x failed\n", port_base+2);
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("do_initialize: sys_outb select failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
2005-07-29 14:44:42 +02:00
|
|
|
irq_hook_id = 0;
|
2007-08-06 13:17:08 +02:00
|
|
|
if(sys_irqsetpolicy(PRINTER_IRQ, 0, &irq_hook_id) != OK ||
|
|
|
|
sys_irqenable(&irq_hook_id) != OK) {
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("do_initialize: irq enabling failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
2005-04-21 16:53:53 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/*==========================================================================*
|
|
|
|
* prepare_output *
|
|
|
|
*==========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void prepare_output()
|
2005-04-21 16:53:53 +02:00
|
|
|
{
|
|
|
|
/* Start next chunk of printer output. Fetch the data from user space. */
|
2006-06-20 11:49:02 +02:00
|
|
|
int s;
|
2005-04-21 16:53:53 +02:00
|
|
|
register int chunk;
|
|
|
|
|
|
|
|
if ( (chunk = user_left) > sizeof obuf) chunk = sizeof obuf;
|
2011-03-25 11:45:57 +01:00
|
|
|
|
Server/driver protocols: no longer allow third-party copies.
Before safecopies, the IO_ENDPT and DL_ENDPT message fields were needed
to know which actual process to copy data from/to, as that process may
not always be the caller. Now that we have full safecopy support, these
fields have become useless for that purpose: the owner of the grant is
*always* the caller. Allowing the caller to supply another endpoint is
in fact dangerous, because the callee may then end up using a grant
from a third party. One could call this a variant of the confused
deputy problem.
From now on, safecopy calls should always use the caller's endpoint as
grant owner. This fully obsoletes the DL_ENDPT field in the
inet/ethernet protocol. IO_ENDPT has other uses besides identifying the
grant owner though. This patch renames IO_ENDPT to USER_ENDPT, not only
because that is a more fitting name (it should never be used for I/O
after all), but also in order to intentionally break any old system
source code outside the base system. If this patch breaks your code,
fixing it is fairly simple:
- DL_ENDPT should be replaced with m_source;
- IO_ENDPT should be replaced with m_source when used for safecopies;
- IO_ENDPT should be replaced with USER_ENDPT for any other use, e.g.
when setting REP_ENDPT, matching requests in CANCEL calls, getting
DEV_SELECT flags, and retrieving of the real user process's endpoint
in DEV_OPEN.
The changes in this patch are binary backward compatible.
2011-04-11 19:35:05 +02:00
|
|
|
s=sys_safecopyfrom(caller, grant_nr, user_vir_d, (vir_bytes) obuf,
|
2012-06-16 03:46:15 +02:00
|
|
|
chunk);
|
2006-06-20 11:49:02 +02:00
|
|
|
|
|
|
|
if(s != OK) {
|
2005-04-21 16:53:53 +02:00
|
|
|
done_status = EFAULT;
|
|
|
|
output_done();
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
optr = obuf;
|
|
|
|
oleft = chunk;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*===========================================================================*
|
|
|
|
* do_printer_output *
|
|
|
|
*===========================================================================*/
|
2012-03-25 20:25:53 +02:00
|
|
|
static void do_printer_output()
|
2005-04-21 16:53:53 +02:00
|
|
|
{
|
2009-09-29 20:47:56 +02:00
|
|
|
/* This function does the actual output to the printer. This is called on an
|
|
|
|
* interrupt message sent from the generic interrupt handler that 'forwards'
|
|
|
|
* interrupts to this driver. The generic handler did not reenable the printer
|
|
|
|
* IRQ yet!
|
2005-04-21 16:53:53 +02:00
|
|
|
*/
|
|
|
|
|
2012-03-05 00:11:41 +01:00
|
|
|
u32_t status;
|
2005-04-21 16:53:53 +02:00
|
|
|
pvb_pair_t char_out[3];
|
|
|
|
|
|
|
|
if (oleft == 0) {
|
|
|
|
/* Nothing more to print. Turn off printer interrupts in case they
|
|
|
|
* are level-sensitive as on the PS/2. This should be safe even
|
|
|
|
* when the printer is busy with a previous character, because the
|
|
|
|
* interrupt status does not affect the printer.
|
|
|
|
*/
|
2007-08-06 13:17:08 +02:00
|
|
|
if(sys_outb(port_base + 2, PR_SELECT) != OK) {
|
|
|
|
printf("printer: sys_outb of %x failed\n", port_base+2);
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("sys_outb failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
|
|
|
if(sys_irqenable(&irq_hook_id) != OK) {
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("sys_irqenable failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
2005-04-21 16:53:53 +02:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
do {
|
|
|
|
/* Loop to handle fast (buffered) printers. It is important that
|
|
|
|
* processor interrupts are not disabled here, just printer interrupts.
|
|
|
|
*/
|
2007-08-06 13:17:08 +02:00
|
|
|
if(sys_inb(port_base + 1, &status) != OK) {
|
|
|
|
printf("printer: sys_inb of %x failed\n", port_base+1);
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("sys_inb failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
2005-04-21 16:53:53 +02:00
|
|
|
if ((status & STATUS_MASK) == BUSY_STATUS) {
|
|
|
|
/* Still busy with last output. This normally happens
|
|
|
|
* immediately after doing output to an unbuffered or slow
|
|
|
|
* printer. It may happen after a call from prepare_output or
|
|
|
|
* pr_restart, since they are not synchronized with printer
|
|
|
|
* interrupts. It may happen after a spurious interrupt.
|
|
|
|
*/
|
2007-08-06 13:17:08 +02:00
|
|
|
if(sys_irqenable(&irq_hook_id) != OK) {
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("sys_irqenable failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
2005-04-21 16:53:53 +02:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
if ((status & STATUS_MASK) == NORMAL_STATUS) {
|
|
|
|
/* Everything is all right. Output another character. */
|
2007-09-11 13:22:29 +02:00
|
|
|
pv_set(char_out[0], port_base, *optr);
|
|
|
|
optr++;
|
2005-04-21 16:53:53 +02:00
|
|
|
pv_set(char_out[1], port_base+2, ASSERT_STROBE);
|
|
|
|
pv_set(char_out[2], port_base+2, NEGATE_STROBE);
|
2007-08-06 13:17:08 +02:00
|
|
|
if(sys_voutb(char_out, 3) != OK) {
|
|
|
|
/* request series of port outb */
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("sys_voutb failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
2005-04-21 16:53:53 +02:00
|
|
|
|
2006-06-20 11:49:02 +02:00
|
|
|
user_vir_d++;
|
2005-04-21 16:53:53 +02:00
|
|
|
user_left--;
|
|
|
|
} else {
|
|
|
|
/* Error. This would be better ignored (treat as busy). */
|
|
|
|
done_status = status;
|
|
|
|
output_done();
|
2007-08-06 13:17:08 +02:00
|
|
|
if(sys_irqenable(&irq_hook_id) != OK) {
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("sys_irqenable failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
2005-04-21 16:53:53 +02:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
while (--oleft != 0);
|
|
|
|
|
|
|
|
/* Finished printing chunk OK. */
|
|
|
|
done_status = OK;
|
|
|
|
output_done();
|
2007-08-06 13:17:08 +02:00
|
|
|
if(sys_irqenable(&irq_hook_id) != OK) {
|
2010-03-05 16:05:11 +01:00
|
|
|
panic("sys_irqenable failed");
|
2007-08-06 13:17:08 +02:00
|
|
|
}
|
2005-04-21 16:53:53 +02:00
|
|
|
}
|
|
|
|
|