So the kernel itself doesn't actually "own" any capabilities, just does the bookkeeping and enforcement?

On Mon, Nov 2, 2015 at 7:05 PM, Gernot Heiser <> wrote:
On 3 Nov 2015, at 12:58 , Raymond Jennings <> wrote:

So basically L4 grants IO caps to the network card's io ports to whatever task acts as the network driver, and it's the driver task's job to bang on the card's I/O and hook up with whatever other tasks represent packet/protocol/whatever layers of the ISO 7 layer stack.

More precisely: seL4 hands all rights to all resources to the initial process, whose job is then to initialise the desired system. It would be that process that hands caps to drivers etc.


The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.