The Design and Implementation of the Anykernel and Rump Kernels

120
int
rump_pub_lwproc_rfork(int arg1)
{
int rv;
rump_schedule();
rv = rump_lwproc_rfork(arg1);
rump_unschedule();
}
return rv;
Figure 3.15: Application interface implementation of lwproc rfork().
The backend kernel call is wrapped around the rump kernel entrypoint and exitpoint.
3.6.3 Interfaces Specific to Rump Kernels
Some interfaces are available only in rump kernels, for example the lwp/process
context management interfaces (manual page rump lwproc.3 at A–23). In a similar
fashion to other interface classes we have discussed, we supply autogenerated
prototypes and wrappers.
The application interface names are prefixed with rump_pub_ (shorthand for public).
The respective internal interfaces are prefixed rump_. As an example, we present
the wrapper for rump_pub_lwproc_rfork() in Figure 3.15. The public interface
wraps the internal interface around the entrypoint and exitpoint.
The master files for rump kernel interfaces are contained in the subdirectory of each
faction in an .ifspec file. The script sys/rump/librump/makeifspec.sh analyzes
this file and autogenerates the prototypes and wrappers.
Additionally, there exist bootstrap interfaces which can be called only before the
rump kernel is bootstrapped. An example is rump_boot_sethowto() which sets the