#
d1335fdb |
|
02-Apr-2018 |
Gerwin Klein <gerwin.klein@data61.csiro.au> |
stricter test for max object size The previous test with word_bits was sufficient on 32 bit platforms, but 64 bit platforms may set a much smaller value for seL4_MaxUntypedBits in relation to word_bits.
|
#
ab313d62 |
|
02-Apr-2018 |
Gerwin Klein <gerwin.klein@data61.csiro.au> |
avoid shift overflow for large Untyped's on 64bit platforms
|
#
5fe431f6 |
|
11-Dec-2017 |
Matthew Brecknell <Matthew.Brecknell@data61.csiro.au> |
Fix max object size in range error for retype on 64-bit platforms The expression previously used was correct for current 32-bit platforms, but not for 64-bit platforms.
|
#
df1d9d7e |
|
23-May-2017 |
Anna Lyons <Anna.Lyons@data61.csiro.au> |
trivial: use constant in seL4_UntypedRetype check
|
#
03c71b63 |
|
16-May-2016 |
Thomas Sewell <Thomas.Sewell@nicta.com.au> |
SELFOUR-444: Preemptible zeroing for retype. Change to the order of operations and timing behaviour of invokeUntyped_Retype. The Retype operation now zeroes the entire range of the Untyped cap (if it is being used for the first time) before installing any objects. This avoids the need for long-running initialisation of large objects, whose initial contents are always zero. The initial zeroing phase is preemptible, and may take multiple timeslices to complete.
|
#
8d0ed702 |
|
31-Oct-2016 |
Adrian Danis <Adrian.Danis@data61.csiro.au> |
Use correct seL4_MaxUntypedBits This change uses the seL4_MaxUntypedBits constant in decodeUntypedInvocation when checking the size of the requested allocation. This constant is also changed to be the correct value. The verification team suspects this check is probably unnecessary, but have also resolved not to waste more time investigating.
|
#
048be2be |
|
23-Oct-2016 |
Bamboo <bamboo@keg.ertos.in.nicta.com.au> |
[STYLE_FIX]
|
#
5ebe19a9 |
|
19-Oct-2016 |
Joel Beeren <joel.beeren@nicta.com.au> |
Fix comment in decodeUntypedInvocation to better reflect maximum object sizes after device-untyped changes
|
#
3f9eb7c8 |
|
06-Oct-2016 |
amrzar <azarrabi@nicta.com.au> |
SELFOUR-632: implement cores non-architecture dependent structres
|
#
59aa0ccd |
|
30-Aug-2016 |
Xin,Gao <xin.gao@nicta.com.au> |
SELFOUR-421: minor changes for c-refine
|
#
d507b2d3 |
|
09-Feb-2016 |
Adrian Danis <Adrian.Danis@nicta.com.au> |
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
|
#
98428013 |
|
25-May-2016 |
Adrian Danis <Adrian.Danis@data61.csiro.au> |
SELFOUR-433: Shift as a 32-bit value Shifting as an unsigned long long does not work on some ARM compilers as the kernel is not linked against libgcc
|
#
73a54b0c |
|
25-May-2016 |
Adrian Danis <Adrian.Danis@data61.csiro.au> |
SELFOUR-433: Prevent undefined shift in userError message
|
#
d93699c9 |
|
04-Jan-2016 |
Anna Lyons <Anna.Lyons@nicta.com.au> |
SELFOUR-114: remove duplication of seL4_MessageInfo_t, adjust naming to avoid cparser mangling
|
#
0ecff9f3 |
|
09-Nov-2015 |
Adrian Danis <Adrian.Danis@nicta.com.au> |
unsigned int -> word_t
|
#
c3dec902 |
|
13-Jul-2015 |
Thomas Sewell <thomas.sewell@nicta.com.au> |
Fix style and unused variable warnings.
|
#
67d8d041 |
|
14-May-2015 |
Thomas Sewell <Thomas.Sewell@nicta.com.au> |
Ghost assertions about max object size.
|
#
91b7da86 |
|
17-Jul-2014 |
TrusthworthySystems <gatekeeper@sel4.systems> |
Release snapshot
|