Moved sched library to components/lib/sl, that creates static libraries for core sl (should I name it libsl_core.a?), fprr module, thd_static_backend module and sl_lock module.
Renamed new_boot to llbooter, as new_boot means nothing. And also, moved boot_test directory into implementation/tests/, which is where I think it should be.
Restructuring sl library directory in composite was pending from previous PR.
One other minor change is - style feedback fix that I missed in incorporating.
Wanted to do this quickly so I can use sl in vkernel stuff by simply linking to it!
@gparmer @Others
Intent for your PR
Choose one (Mandatory):
[ ] This PR is for a code-review and is intended to get feedback, but not to be pulled yet.
[x] This PR is mature, and ready to be integrated into the repo.
Code Quality
As part of this pull request, I've considered the following:
[x] I've made an attempt to remove all redundant code: Note:This PR is mainly about moving files to appropriate places
[x] I've considered ways in which my changes might impact existing code, and cleaned it up
[x] I've formatted the code in an effort to make it easier to read (proper error handling, function use, etc...)
[x] I've commented appropriately where code is tricky
[x] I agree that there is no "throw-away" code, and that code in this PR is of high quality
Testing
I've tested the code using the following test programs (provide list here):
*"(Tested only on Qemu, mainly tested to see if all tests run to completion)**
Summary of this Pull Request (PR)
components/lib/sl
, that creates static libraries for core sl (should I name it libsl_core.a?), fprr module, thd_static_backend module and sl_lock module.new_boot
tollbooter
, asnew_boot
means nothing. And also, movedboot_test
directory intoimplementation/tests/
, which is where I think it should be.Restructuring sl library directory in composite was pending from previous PR. One other minor change is - style feedback fix that I missed in incorporating.
Wanted to do this quickly so I can use sl in vkernel stuff by simply linking to it!
@gparmer @Others
Intent for your PR
Choose one (Mandatory):
Code Quality
As part of this pull request, I've considered the following:
Style:
Code Craftsmanship:
Testing
I've tested the code using the following test programs (provide list here): *"(Tested only on Qemu, mainly tested to see if all tests run to completion)**