L4Re - L4 Runtime Environment
Related Pages
Here is a list of all related documentation pages:
[detail level 123]
 IntroductionThe intention of this section is to provide a short overview about the L4Re environment
 TutorialThis tutorial assumes that the reader is familiar with the basic L4 concepts that were discussed in the Introduction section and has a working knowledge of C++
 Programming for L4ReThis part of the documentation discusses the concept of microkernel-based programming in more detail
 Capabilities and NamingThe L4Re system is a capability based system which uses and offers capabilities to implement fine-grained access control
 Initial Environment and Application BootstrappingNew applications that are started by a loader conforming to L4Re get provided an Initial Environment
 Memory management - Data Spaces and the Region Map
 Program Input and OutputThe initial environment provides a Vcon capability used as the standard input/output stream
 Initial Memory Allocator and FactoryThe purpose of the memory allocator and of the factory is to provide the application with the means to allocate memory (in the form of data spaces) and kernel objects respectively
 Application and Server Building BlocksSo far we have discussed the environment of applications in which a single thread runs and which may invoke services provided through their initial objects
 Pthread SupportL4Re supports the standard pthread library functionality
 Interface Definition LanguageAn interface definition in L4Re is normally declared as a class derived from L4::Kobject_t
 L4Re Build SystemL4Re uses a custom make-based build system, often simply referred to as BID
 prog.mk - Application RoleThe prog role is used to build executable programs
 include.mk - Header File RoleThe header file role is responsible for installing header file at the appropriate location
 test.mk - Test Application RoleThe test role is very similar to the application role, it also builds an executable binary
 L4Re ServersHere you shall find a quick overview over the standard services running on Fiasco.OC and L4Re
 Moe, the Root-TaskMoe is the default root-task implementation for L4Re-based systems
 Ned, the Init ProcessNed's job is to bootstrap the system running on L4Re
 Io, the Io ServerThe Io server handles all platform devices and resources such as I/O memory, ports (on x86) and interrupts, and grants access to those to clients
 Cons, the Console MultiplexerCons allows to multiplex console output from different L4 clients to different L4::Vcon-capable in/output servers
 Mag, the GUI MultiplexerMag is the default multiplexer for graphics hardware
 Uvmm, the virtual machine monitor

How to enable guest suspend/resume

 Deprecated List