Inspect L4Linux Memory

Marcus Voelp voelp at
Sat Sep 10 06:13:08 CEST 2005

there are actually two nice ways how you can access L4Linux kernel 
memory. The first is to install a driver to L4Linux which creates an L4 
thread that in turn would read out the memory when requested to do so. 
The second is mapping the L4Linux memory to your external observer by 
sharing the dataspace that provides L4Linux with memory.

The first solution obviously is not suited when reading out much data 
and you also rely on the thread to live (i.e., if Linux crashes there is 
the chance that the driver thread crashes as well). The second solution 
provides a faster read access and survives also kernel crashes.


Julian Grizzard wrote:

>Hi all,
>I am running L4Linux 2.6 on Fiasco using L4Env.  I would like to build
>an isolated L4 task that can inspect the contents of the L4Linux task
>state.  Any pointers on the best way to do this?  Conceivably, I could
>map the contents of the L4Linux task into my isolated L4 task to read
>the memory, but I'm not sure the best way to do this.
>l4-hackers mailing list
>l4-hackers at

More information about the l4-hackers mailing list