seL4/include/object
Adrian Danis d507b2d39e SELFOUR-421 Introduce explicit device frames and untypeds
Kernel objects cannot be created from device untypeds, with the
exception of frames, which do not get zeroed and cannot be used
as an IPC buffer. Device untypeds additionally cannot be used
in the construction of ASID pools.

This then changes the API to the rootserver (i.e. bootinfo) to
send device untypeds instead of device frames. On ARM these
device untypeds are the same as the previously exported device
frame regions. On x86 PCI scanning is removed and all physical
memory addresses (that are not important for kernel integrity)
are released to the user.

In order to have bits in the frame and untyped caps on ARM the
number of software ASIDs had to be reduced from 2^18 to 2^17,
and the maximum untyped size reduced from 2^31 to 2^30
2016-09-23 14:15:08 +10:00
..
cnode.h SELFOUR-114: remove duplication of seL4_MessageInfo_t, adjust naming to avoid cparser mangling 2016-01-11 11:16:08 +11:00
endpoint.h SELFOUR-317: rename async endpoint to notification object, and other 2015-11-09 17:18:43 +11:00
interrupt.h x86: IOAPIC/MSI syscalls 2016-02-02 15:58:18 +11:00
notification.h SELFOUR-317: rename async endpoint to notification object, and other 2015-11-09 17:18:43 +11:00
objecttype.h SELFOUR-421 Introduce explicit device frames and untypeds 2016-09-23 14:15:08 +10:00
structures.h SELFOUR-566: Decouble seL4_DebugNameThread from CONFIG_PRINTING 2016-07-15 12:30:17 +10:00
structures_32.bf SELFOUR-421 Introduce explicit device frames and untypeds 2016-09-23 14:15:08 +10:00
tcb.h SELFOUR-566: Decouble seL4_DebugNameThread from CONFIG_PRINTING 2016-07-15 12:30:17 +10:00
untyped.h SELFOUR-421 Introduce explicit device frames and untypeds 2016-09-23 14:15:08 +10:00