URL
https://opencores.org/ocsvn/c0or1k/c0or1k/trunk
Details |
Compare with Previous |
View Log
| Line No. |
Rev |
Author |
Line |
| 1 |
2 |
drasko |
|
| 2 |
|
|
Missing tests:
|
| 3 |
|
|
|
| 4 |
|
|
1) Library tests:
|
| 5 |
|
|
~~~~~~~~~~~~~~~~~
|
| 6 |
|
|
- L4Lib Thread library needs to be tested
|
| 7 |
|
|
- Stack allocation
|
| 8 |
|
|
- UTCB allocation
|
| 9 |
|
|
- L4Lib Capability library needs to be tested
|
| 10 |
|
|
- Capability read, print, manipulation
|
| 11 |
|
|
|
| 12 |
|
|
- Address allocation, id allocation functions need to be tested.
|
| 13 |
|
|
|
| 14 |
|
|
- Page allocator needs to be tested.
|
| 15 |
|
|
- Memcache needs to be tested.
|
| 16 |
|
|
- All above libraries must be tested with many many different combinations.
|
| 17 |
|
|
|
| 18 |
|
|
|
| 19 |
|
|
2) API Tests:
|
| 20 |
|
|
~~~~~~~~~~~~~
|
| 21 |
|
|
- Null pointer tests
|
| 22 |
|
|
- Extended IPC via page faulting.
|
| 23 |
|
|
- Mutex tests on different virtual but same physical page.
|
| 24 |
|
|
- Cache flushing tests
|
| 25 |
|
|
- Capability limit tests (e.g. pushing limits of given capabilities)
|
| 26 |
|
|
- Capability manipulation tests (manipulating existing capabilities)
|
| 27 |
|
|
|
| 28 |
|
|
3) Performance Tests:
|
| 29 |
|
|
~~~~~~~~~~~~~~~~~~~~~
|
| 30 |
|
|
Performance tests should fall back to using timer if perfmon does not exist.
|
| 31 |
|
|
Performance tests need to run on multiple architectures.
|
| 32 |
|
|
(e.g. beagleboard perfmon, timer ...)
|
| 33 |
|
|
- Map/unmap
|
| 34 |
|
|
- Ipc results are missing
|
© copyright 1999-2024
OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.