2005-04-21 16:53:53 +02:00
|
|
|
#ifndef _IPC_H
|
|
|
|
#define _IPC_H
|
|
|
|
|
2010-03-23 01:09:11 +01:00
|
|
|
#include <minix/ipcconst.h>
|
2008-11-19 13:26:10 +01:00
|
|
|
#include <minix/type.h>
|
2012-06-10 19:50:17 +02:00
|
|
|
#include <minix/const.h>
|
2008-11-19 13:26:10 +01:00
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
/*==========================================================================*
|
|
|
|
* Types relating to messages. *
|
|
|
|
*==========================================================================*/
|
|
|
|
|
|
|
|
#define M1 1
|
|
|
|
#define M3 3
|
|
|
|
#define M4 4
|
2010-01-13 00:08:50 +01:00
|
|
|
#define M3_STRING 14 /* legacy m3_ca1 size (must not be changed) */
|
|
|
|
#define M3_LONG_STRING 16 /* current m3_ca1 size (may be increased) */
|
2005-04-21 16:53:53 +02:00
|
|
|
|
|
|
|
typedef struct {int m1i1, m1i2, m1i3; char *m1p1, *m1p2, *m1p3;} mess_1;
|
2006-10-25 15:40:36 +02:00
|
|
|
typedef struct {int m2i1, m2i2, m2i3; long m2l1, m2l2; char *m2p1;
|
|
|
|
short m2s1;} mess_2;
|
2010-01-13 00:08:50 +01:00
|
|
|
typedef struct {int m3i1, m3i2; char *m3p1; char m3ca1[M3_LONG_STRING];} mess_3;
|
2005-04-21 16:53:53 +02:00
|
|
|
typedef struct {long m4l1, m4l2, m4l3, m4l4, m4l5;} mess_4;
|
2010-01-19 22:19:59 +01:00
|
|
|
typedef struct {short m5s1, m5s2; int m5i1, m5i2; long m5l1, m5l2, m5l3;}mess_5;
|
2006-10-25 15:40:36 +02:00
|
|
|
typedef struct {long m6l1, m6l2, m6l3; short m6s1, m6s2, m6s3; char m6c1, m6c2;
|
|
|
|
char *m6p1, *m6p2;} mess_6;
|
2010-09-23 12:49:42 +02:00
|
|
|
typedef struct {int m7i1, m7i2, m7i3, m7i4, m7i5; char *m7p1, *m7p2;} mess_7;
|
2005-06-06 13:40:32 +02:00
|
|
|
typedef struct {int m8i1, m8i2; char *m8p1, *m8p2, *m8p3, *m8p4;} mess_8;
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
typedef struct {long m9l1, m9l2, m9l3, m9l4, m9l5;
|
|
|
|
short m9s1, m9s2, m9s3, m9s4; } mess_9;
|
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
|
|
|
typedef struct {int m10i1, m10i2, m10i3, m10i4;
|
|
|
|
long m10l1, m10l2, m10l3; } mess_10;
|
2005-04-21 16:53:53 +02:00
|
|
|
|
2013-03-20 20:18:52 +01:00
|
|
|
typedef struct {
|
|
|
|
void *block;
|
|
|
|
u32_t dev_offset_pages;
|
|
|
|
u32_t ino_offset_pages;
|
|
|
|
u32_t ino;
|
|
|
|
u32_t *flags_ptr;
|
|
|
|
u32_t dev;
|
|
|
|
u8_t pages;
|
|
|
|
u8_t flags;
|
2013-05-31 22:37:25 +02:00
|
|
|
} mess_vmmcp;
|
2013-03-20 20:18:52 +01:00
|
|
|
|
|
|
|
typedef struct {
|
|
|
|
endpoint_t who;
|
|
|
|
u32_t offset;
|
|
|
|
u32_t dev;
|
|
|
|
u32_t ino;
|
|
|
|
u32_t vaddr;
|
|
|
|
u32_t len;
|
|
|
|
u16_t fd;
|
|
|
|
u16_t clearend_and_flags; /* low 12 bits are clearend, rest flags */
|
2013-05-31 22:37:25 +02:00
|
|
|
} mess_vm_vfs_mmap;
|
2013-03-20 20:18:52 +01:00
|
|
|
|
2013-05-31 22:37:25 +02:00
|
|
|
typedef struct { u8_t flags; void *addr; } mess_vmmcp_reply;
|
2013-03-20 20:18:52 +01:00
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
typedef struct {
|
. introduced DEV_READ_S, DEV_WRITE_S, DEV_SCATTER_S, DEV_GATHER_S
and DEV_IOCTL_S as replacements for DEV_READ, DEV_WRITE, DEV_SCATTER,
DEV_GATHER and DEV_IOCTL. Instead of a direct address, the *_S commands
pass 'grant ids' to the drivers which are referenced through a new set
of copy calls (sys_safecopyfrom and sys_safecopyto). in order for this
copy to succeed, the grant must have previously been created in the
address space of the granter.
. bitmap manipulation functions moved to <minix/bitmap.h>
. HIGHPOS introduced as field containing high 32 bits of position in
device I/O message; TTY_FLAGS no longer used
. IO_GRANT field introduced for GRANTs, to replace ADDRESS
. REP_IO_GRANT field for un-SUSPEND messages introduced to indicate
grant for which I/O was done to disambiguate messages
. SYS_SAFECOPYFROM and SYS_SAFECOPYTO introduced as new calls
. SYS_PRIV_SET_GRANTS code introduced as a code to set the address and
size of the grant table in a process' own address space
. 'type' and 'direction' field of _ins* and _outs* I/O functions
are merged into one by ORing _DIO_INPUT/_DIO_OUTPUT and _DIO_BYTE/_DIO_WORD
etc. This allows for an additional parameter, _DIO_SAFE, which indicates
the address in another address space isn't actually an address, but
a grant id. Also needs an offset, for which fields had to be merged.
. SCP_* are field names for SYS_SAFECOPY* functions
. DIAGNOSTICS and GET_KMESS moved to their own range above DIAG_BASE,
added DIAGNOSTICS_S which is a grant-based variant of DIAGNOSTICS
. removed obsolete BINCOMPAT and SRCCOMPAT options
. added GRANT_SEG type for use in vircopy - allows copying to a grant
id (without offset)
. added _MINIX_IOCTL_* macros that decode information encoded by
_IO* macros in ioctl codes, used to check which grants are necessary
for an ioctl
. introduced the type endpoint_t for process endpoints, changed some
prototypes and struct field types to match
. renamed protected to prot for g++
2006-06-20 10:38:15 +02:00
|
|
|
endpoint_t m_source; /* who sent the message */
|
2005-04-21 16:53:53 +02:00
|
|
|
int m_type; /* what kind of message is it */
|
|
|
|
union {
|
|
|
|
mess_1 m_m1;
|
|
|
|
mess_2 m_m2;
|
|
|
|
mess_3 m_m3;
|
|
|
|
mess_4 m_m4;
|
|
|
|
mess_5 m_m5;
|
|
|
|
mess_7 m_m7;
|
2005-06-06 13:40:32 +02:00
|
|
|
mess_8 m_m8;
|
2006-10-25 15:40:36 +02:00
|
|
|
mess_6 m_m6;
|
2007-08-07 13:56:28 +02:00
|
|
|
mess_9 m_m9;
|
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
|
|
|
mess_10 m_m10;
|
2013-03-20 20:18:52 +01:00
|
|
|
mess_vmmcp m_vmmcp;
|
|
|
|
mess_vmmcp_reply m_vmmcp_reply;
|
|
|
|
mess_vm_vfs_mmap m_vm_vfs;
|
2005-04-21 16:53:53 +02:00
|
|
|
} m_u;
|
2012-06-29 13:39:40 +02:00
|
|
|
} message __aligned(16);
|
2005-04-21 16:53:53 +02:00
|
|
|
|
|
|
|
/* The following defines provide names for useful members. */
|
|
|
|
#define m1_i1 m_u.m_m1.m1i1
|
|
|
|
#define m1_i2 m_u.m_m1.m1i2
|
|
|
|
#define m1_i3 m_u.m_m1.m1i3
|
|
|
|
#define m1_p1 m_u.m_m1.m1p1
|
|
|
|
#define m1_p2 m_u.m_m1.m1p2
|
|
|
|
#define m1_p3 m_u.m_m1.m1p3
|
|
|
|
|
|
|
|
#define m2_i1 m_u.m_m2.m2i1
|
|
|
|
#define m2_i2 m_u.m_m2.m2i2
|
|
|
|
#define m2_i3 m_u.m_m2.m2i3
|
|
|
|
#define m2_l1 m_u.m_m2.m2l1
|
|
|
|
#define m2_l2 m_u.m_m2.m2l2
|
|
|
|
#define m2_p1 m_u.m_m2.m2p1
|
|
|
|
|
2006-10-25 15:40:36 +02:00
|
|
|
#define m2_s1 m_u.m_m2.m2s1
|
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
#define m3_i1 m_u.m_m3.m3i1
|
|
|
|
#define m3_i2 m_u.m_m3.m3i2
|
|
|
|
#define m3_p1 m_u.m_m3.m3p1
|
|
|
|
#define m3_ca1 m_u.m_m3.m3ca1
|
|
|
|
|
|
|
|
#define m4_l1 m_u.m_m4.m4l1
|
|
|
|
#define m4_l2 m_u.m_m4.m4l2
|
|
|
|
#define m4_l3 m_u.m_m4.m4l3
|
|
|
|
#define m4_l4 m_u.m_m4.m4l4
|
|
|
|
#define m4_l5 m_u.m_m4.m4l5
|
|
|
|
|
2010-01-19 22:19:59 +01:00
|
|
|
#define m5_s1 m_u.m_m5.m5s1
|
|
|
|
#define m5_s2 m_u.m_m5.m5s2
|
2005-04-21 16:53:53 +02:00
|
|
|
#define m5_i1 m_u.m_m5.m5i1
|
|
|
|
#define m5_i2 m_u.m_m5.m5i2
|
|
|
|
#define m5_l1 m_u.m_m5.m5l1
|
|
|
|
#define m5_l2 m_u.m_m5.m5l2
|
|
|
|
#define m5_l3 m_u.m_m5.m5l3
|
|
|
|
|
2006-10-25 15:40:36 +02:00
|
|
|
#define m6_l1 m_u.m_m6.m6l1
|
|
|
|
#define m6_l2 m_u.m_m6.m6l2
|
|
|
|
#define m6_l3 m_u.m_m6.m6l3
|
|
|
|
#define m6_s1 m_u.m_m6.m6s1
|
|
|
|
#define m6_s2 m_u.m_m6.m6s2
|
|
|
|
#define m6_s3 m_u.m_m6.m6s3
|
|
|
|
#define m6_c1 m_u.m_m6.m6c1
|
|
|
|
#define m6_c2 m_u.m_m6.m6c2
|
|
|
|
#define m6_p1 m_u.m_m6.m6p1
|
|
|
|
#define m6_p2 m_u.m_m6.m6p2
|
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
#define m7_i1 m_u.m_m7.m7i1
|
|
|
|
#define m7_i2 m_u.m_m7.m7i2
|
|
|
|
#define m7_i3 m_u.m_m7.m7i3
|
|
|
|
#define m7_i4 m_u.m_m7.m7i4
|
2010-09-23 12:49:42 +02:00
|
|
|
#define m7_i5 m_u.m_m7.m7i5
|
2005-04-21 16:53:53 +02:00
|
|
|
#define m7_p1 m_u.m_m7.m7p1
|
|
|
|
#define m7_p2 m_u.m_m7.m7p2
|
|
|
|
|
2005-06-06 13:40:32 +02:00
|
|
|
#define m8_i1 m_u.m_m8.m8i1
|
|
|
|
#define m8_i2 m_u.m_m8.m8i2
|
|
|
|
#define m8_p1 m_u.m_m8.m8p1
|
|
|
|
#define m8_p2 m_u.m_m8.m8p2
|
|
|
|
#define m8_p3 m_u.m_m8.m8p3
|
|
|
|
#define m8_p4 m_u.m_m8.m8p4
|
|
|
|
|
2007-08-07 13:56:28 +02:00
|
|
|
#define m9_l1 m_u.m_m9.m9l1
|
|
|
|
#define m9_l2 m_u.m_m9.m9l2
|
|
|
|
#define m9_l3 m_u.m_m9.m9l3
|
|
|
|
#define m9_l4 m_u.m_m9.m9l4
|
|
|
|
#define m9_l5 m_u.m_m9.m9l5
|
|
|
|
#define m9_s1 m_u.m_m9.m9s1
|
|
|
|
#define m9_s2 m_u.m_m9.m9s2
|
|
|
|
#define m9_s3 m_u.m_m9.m9s3
|
- Introduce support for sticky bit.
- Revise VFS-FS protocol and update VFS/MFS/ISOFS accordingly.
- Clean up MFS by removing old, dead code (backwards compatibility is broken by
the new VFS-FS protocol, anyway) and rewrite other parts. Also, make sure all
functions have proper banners and prototypes.
- VFS should always provide a (syntactically) valid path to the FS; no need for
the FS to do sanity checks when leaving/entering mount points.
- Fix several bugs in MFS:
- Several path lookup bugs in MFS.
- A link can be too big for the path buffer.
- A mountpoint can become inaccessible when the creation of a new inode
fails, because the inode already exists and is a mountpoint.
- Introduce support for supplemental groups.
- Add test 46 to test supplemental group functionality (and removed obsolete
suppl. tests from test 2).
- Clean up VFS (not everything is done yet).
- ISOFS now opens device read-only. This makes the -r flag in the mount command
unnecessary (but will still report to be mounted read-write).
- Introduce PipeFS. PipeFS is a new FS that handles all anonymous and
named pipes. However, named pipes still reside on the (M)FS, as they are part
of the file system on disk. To make this work VFS now has a concept of
'mapped' inodes, which causes read, write, truncate and stat requests to be
redirected to the mapped FS, and all other requests to the original FS.
2009-12-20 21:27:14 +01:00
|
|
|
#define m9_s4 m_u.m_m9.m9s4
|
2007-08-07 13:56:28 +02:00
|
|
|
|
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
|
|
|
#define m10_i1 m_u.m_m10.m10i1
|
|
|
|
#define m10_i2 m_u.m_m10.m10i2
|
|
|
|
#define m10_i3 m_u.m_m10.m10i3
|
|
|
|
#define m10_i4 m_u.m_m10.m10i4
|
|
|
|
#define m10_l1 m_u.m_m10.m10l1
|
|
|
|
#define m10_l2 m_u.m_m10.m10l2
|
|
|
|
#define m10_l3 m_u.m_m10.m10l3
|
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
/*==========================================================================*
|
|
|
|
* Minix run-time system (IPC). *
|
|
|
|
*==========================================================================*/
|
|
|
|
|
2007-04-23 13:59:19 +02:00
|
|
|
/* Datastructure for asynchronous sends */
|
|
|
|
typedef struct asynmsg
|
|
|
|
{
|
|
|
|
unsigned flags;
|
|
|
|
endpoint_t dst;
|
|
|
|
int result;
|
|
|
|
message msg;
|
|
|
|
} asynmsg_t;
|
|
|
|
|
|
|
|
/* Defines for flags field */
|
2011-04-08 17:14:48 +02:00
|
|
|
#define AMF_EMPTY 000 /* slot is not inuse */
|
|
|
|
#define AMF_VALID 001 /* slot contains message */
|
|
|
|
#define AMF_DONE 002 /* Kernel has processed the message. The
|
2007-04-23 13:59:19 +02:00
|
|
|
* result is stored in 'result'
|
|
|
|
*/
|
2011-04-08 17:14:48 +02:00
|
|
|
#define AMF_NOTIFY 004 /* Send a notification when AMF_DONE is set */
|
|
|
|
#define AMF_NOREPLY 010 /* Not a reply message for a SENDREC */
|
|
|
|
#define AMF_NOTIFY_ERR 020 /* Send a notification when AMF_DONE is set and
|
|
|
|
* delivery of the message failed */
|
2007-04-23 13:59:19 +02:00
|
|
|
|
2012-06-10 19:50:17 +02:00
|
|
|
int _send_orig(endpoint_t dest, message *m_ptr);
|
|
|
|
int _receive_orig(endpoint_t src, message *m_ptr, int *status_ptr);
|
|
|
|
int _sendrec_orig(endpoint_t src_dest, message *m_ptr);
|
|
|
|
int _sendnb_orig(endpoint_t dest, message *m_ptr);
|
|
|
|
int _notify_orig(endpoint_t dest);
|
|
|
|
int _senda_orig(asynmsg_t *table, size_t count);
|
|
|
|
int _do_kernel_call_orig(message *m_ptr);
|
|
|
|
|
2012-07-18 18:53:20 +02:00
|
|
|
int _minix_kernel_info_struct(struct minix_kerninfo **);
|
2012-03-24 16:16:34 +01:00
|
|
|
|
2012-11-14 23:00:29 +01:00
|
|
|
/* Hide names to avoid name space pollution. */
|
|
|
|
#define notify _notify
|
|
|
|
#define sendrec _sendrec
|
|
|
|
#define receive _receive
|
|
|
|
#define receivenb _receivenb
|
|
|
|
#define send _send
|
|
|
|
#define sendnb _sendnb
|
|
|
|
#define senda _senda
|
|
|
|
|
2012-06-10 19:50:17 +02:00
|
|
|
struct minix_ipcvecs {
|
2012-11-14 23:14:48 +01:00
|
|
|
int (*send)(endpoint_t dest, message *m_ptr);
|
|
|
|
int (*receive)(endpoint_t src, message *m_ptr, int *st);
|
|
|
|
int (*sendrec)(endpoint_t src_dest, message *m_ptr);
|
|
|
|
int (*sendnb)(endpoint_t dest, message *m_ptr);
|
|
|
|
int (*notify)(endpoint_t dest);
|
|
|
|
int (*do_kernel_call)(message *m_ptr);
|
|
|
|
int (*senda)(asynmsg_t *table, size_t count);
|
2012-06-10 19:50:17 +02:00
|
|
|
};
|
|
|
|
|
|
|
|
/* kernel-set IPC vectors retrieved by a constructor in libc/sys-minix/init.c */
|
|
|
|
extern struct minix_ipcvecs _minix_ipcvecs;
|
|
|
|
|
2012-11-14 23:00:29 +01:00
|
|
|
static inline int _send(endpoint_t dest, message *m_ptr)
|
|
|
|
{
|
2012-11-14 23:14:48 +01:00
|
|
|
return _minix_ipcvecs.send(dest, m_ptr);
|
2012-11-14 23:00:29 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline int _receive(endpoint_t src, message *m_ptr, int *st)
|
|
|
|
{
|
2012-11-14 23:14:48 +01:00
|
|
|
return _minix_ipcvecs.receive(src, m_ptr, st);
|
2012-11-14 23:00:29 +01:00
|
|
|
}
|
2012-06-10 19:50:17 +02:00
|
|
|
|
2012-11-14 23:00:29 +01:00
|
|
|
static inline int _sendrec(endpoint_t src_dest, message *m_ptr)
|
|
|
|
{
|
2012-11-14 23:14:48 +01:00
|
|
|
return _minix_ipcvecs.sendrec(src_dest, m_ptr);
|
2012-11-14 23:00:29 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline int _sendnb(endpoint_t dest, message *m_ptr)
|
|
|
|
{
|
2013-06-11 17:13:52 +02:00
|
|
|
return _minix_ipcvecs.sendnb(dest, m_ptr);
|
2012-11-14 23:00:29 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline int _notify(endpoint_t dest)
|
|
|
|
{
|
2012-11-14 23:14:48 +01:00
|
|
|
return _minix_ipcvecs.notify(dest);
|
2012-11-14 23:00:29 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline int do_kernel_call(message *m_ptr)
|
|
|
|
{
|
2012-11-14 23:14:48 +01:00
|
|
|
return _minix_ipcvecs.do_kernel_call(m_ptr);
|
2012-11-14 23:00:29 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline int _senda(asynmsg_t *table, size_t count)
|
|
|
|
{
|
2012-11-14 23:14:48 +01:00
|
|
|
return _minix_ipcvecs.senda(table, count);
|
2012-11-14 23:00:29 +01:00
|
|
|
}
|
2010-02-09 16:20:09 +01:00
|
|
|
|
2005-04-21 16:53:53 +02:00
|
|
|
#endif /* _IPC_H */
|