Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
fd1ad431e8
NetBSD/sys/rump/librump/rumpkern/rumpkern.ifspec

33 lines
927 B
Plaintext
Raw Normal View History

There is a use case where preserving the parent's fd table is relevant, so to accommodate that change rump_lwproc_newproc() to rump_lwproc_rfork(). The new interface has the rfork() fd table semantics. The equivalent of rump_lwproc_newproc() is rump_lwproc_rfork(RUMP_RFCFDG).
2011-01-02 15:52:25 +03:00
; $NetBSD: rumpkern.ifspec,v 1.10 2011/01/02 12:52:25 pooka Exp $
Create rump public interfaces from description tables. This allows us to control and wrap all entry points from "userspace" into rump. This in turn is necessary for the upcoming rump cpu scheduler. For each interface "foo" a public wrapper called "rump_foo" is created. It calls the internal implementation "rumppriv_foo". In case foo is to be called from inside of rump kernel space, the private interface "rumppriv_foo" is used -- the userspace wrapper prototypes are not even exported into the rump kernel namespace. Needless to say, the rump kernel internal interfaces are not exported for users. Now, three classes of interfaces fight for control of rump: + the noble local control interfaces (which this commit addresses) + the insidious rump system calls (which are generated from syscalls.master) + and the evil vnode interfaces (which are generated from vnode_if.src)
2009-10-14 21:17:00 +04:00
NAME|kern
PUBHDR|include/rump/rumpkern_if_pub.h
PRIVHDR|librump/rumpkern/rumpkern_if_priv.h
WRAPPERS|librump/rumpkern/rumpkern_if_wrappers.c
; type | name | args
;
int |getversion |void
Use improved kernel module interfaces: instead of adding + loading modules in bootstrap, just add them. Load them later the same way as the kernel does: module_init_class(). Change the signature of rump_module_init() to take a vector instead of just one module. All modules in a DSO should be init'd at the same time because they might depend on each other, and code outside the rump kernel cannot know which way. (binary kernel modules are still loaded with rump_sys_modctl() the usual way).
2010-03-05 21:41:46 +03:00
int |module_init |const struct modinfo * const *, size_t
int |module_fini |const struct modinfo *
Add rump_kernelfsym_load(), which loads the kernel symbol table.
2009-11-26 12:20:07 +03:00
int |kernelfsym_load|void *, uint64_t, char *, uint64_t
Create rump public interfaces from description tables. This allows us to control and wrap all entry points from "userspace" into rump. This in turn is necessary for the upcoming rump cpu scheduler. For each interface "foo" a public wrapper called "rump_foo" is created. It calls the internal implementation "rumppriv_foo". In case foo is to be called from inside of rump kernel space, the private interface "rumppriv_foo" is used -- the userspace wrapper prototypes are not even exported into the rump kernel namespace. Needless to say, the rump kernel internal interfaces are not exported for users. Now, three classes of interfaces fight for control of rump: + the noble local control interfaces (which this commit addresses) + the insidious rump system calls (which are generated from syscalls.master) + and the evil vnode interfaces (which are generated from vnode_if.src)
2009-10-14 21:17:00 +04:00
struct uio * |uio_setup |void *, size_t, off_t, enum rump_uiorw
size_t |uio_getresid |struct uio *
off_t |uio_getoff |struct uio *
size_t |uio_free |struct uio *
Use "struct kauth_cred *" instead of kauth_cred_t in all exported interfaces. Allows to remove hairbrained _t typedef dance.
2010-04-14 18:12:48 +04:00
struct kauth_cred*|cred_create |uid_t, gid_t, size_t, gid_t *
void |cred_put |struct kauth_cred *
Create rump public interfaces from description tables. This allows us to control and wrap all entry points from "userspace" into rump. This in turn is necessary for the upcoming rump cpu scheduler. For each interface "foo" a public wrapper called "rump_foo" is created. It calls the internal implementation "rumppriv_foo". In case foo is to be called from inside of rump kernel space, the private interface "rumppriv_foo" is used -- the userspace wrapper prototypes are not even exported into the rump kernel namespace. Needless to say, the rump kernel internal interfaces are not exported for users. Now, three classes of interfaces fight for control of rump: + the noble local control interfaces (which this commit addresses) + the insidious rump system calls (which are generated from syscalls.master) + and the evil vnode interfaces (which are generated from vnode_if.src)
2009-10-14 21:17:00 +04:00
Rewrite rump process and lwp allocation routines now that I have some idea of how they should be done. This change essentially moves the responsibility of pid/lwpid management from the application side into the rump kernel. It also introduces clear rules on what happens when, i.e. introduces semantics (these semantics will be documented on the man page, and more importantly in atf tests).
2010-09-01 23:13:38 +04:00
; lwp and proc creation / switching interfaces
There is a use case where preserving the parent's fd table is relevant, so to accommodate that change rump_lwproc_newproc() to rump_lwproc_rfork(). The new interface has the rfork() fd table semantics. The equivalent of rump_lwproc_newproc() is rump_lwproc_rfork(RUMP_RFCFDG).
2011-01-02 15:52:25 +03:00
int |lwproc_rfork |int
Rewrite rump process and lwp allocation routines now that I have some idea of how they should be done. This change essentially moves the responsibility of pid/lwpid management from the application side into the rump kernel. It also introduces clear rules on what happens when, i.e. introduces semantics (these semantics will be documented on the man page, and more importantly in atf tests).
2010-09-01 23:13:38 +04:00
int |lwproc_newlwp |pid_t
void |lwproc_switch |struct lwp *
void |lwproc_releaselwp |void
struct lwp * |lwproc_curlwp |void
void |allbetsareoff_setid |pid_t, int
Reference in New Issue Copy Permalink