History log of /seL4-camkes-master/projects/seL4_libs/libsel4allocman/src/cspace/two_level.c
Revision Date Author Comments
# dc74a3a3 21-Jul-2020 Kent McLeod <Kent.Mcleod@data61.csiro.au>

trivial: style changed file


# 56edd6b5 20-Jul-2020 Kent McLeod <Kent.Mcleod@data61.csiro.au>

trivial: Fix compiler warnings

- Declare unused variables
- Move variable initialization to prevent uninitialized use
- Correctly store bitwise operation result
- Fixup memset calls to use correct size
- Add missing return statement to functions
- Conditionally define functions that are used conditionally


# a60a14c2 17-Jan-2019 James Ye <james.ye@data61.csiro.au>

libsel4allocman: use correct word size


# 0016dfc6 13-Jul-2017 Anna Lyons <Anna.Lyons@data61.csiro.au>

Fix all the whitespace

- remove trailing whitespace
- remove duplicate blank lines
- remove blank lines at end of files


# 9214341c 04-Jun-2017 Anna Lyons <Anna.Lyons@data61.csiro.au>

Fix licenses


# 902a096c 18-Feb-2016 Adrian Danis <Adrian.Danis@nicta.com.au>

libsel4allocman: Memory mapped device IO allocation support

Adds support at the top level allocman interface for allocating
objects at a particular physical address (allocman_utspace_alloc_at)
as well as fullfilling allocations from 'device memory'. Uses this
for implementing the additional vka interface function vka_utspace_alloc_at

The split and twinkle untyped allocators are updated to support this
new interface. split implements the 'alloc_at' by brute force searches
over its untypeds, whilst twinkle with its lack of book keeping
is forced to fail any 'alloc_at' request


# a28279ae 15-May-2016 Matthew Fernandez <matthew.fernandez@nicta.com.au>

libsel4allocman: Fix missing initialised field.

This commit fixes an instance where a struct was initialised with an incorrect
number of fields. The compiler figured out what was meant, so no harm was done,
but the previous code was technically incorrect.


# 14ab04c3 12-Nov-2015 Adrian Danis <Adrian.Danis@nicta.com.au>

libsel4allocman: Make allocman 64-bit friendly

When compiling for 32-bit there may be spurious warnings due to
some interface type changes. These will eventually be fixed when
other libraries are made 64-bit compatible