Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 89 and Version 90 of GSoC/2020


Ignore:
Timestamp:
08/12/20 15:05:02 (4 years ago)
Author:
UTKARSH RAI
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2020

    v89 v90  
    276276           * Complete the test for stack-isolation and sharing by using the high-level APIs
    277277
    278 
    279      
    280 
     278* '''July 29:''' Ninth Meeting
     279      * ''Progress:''
     280           * I spent a major part of the week in resolving the problems in changing memory entries of an allocated stack,
     281             finally, I realized that the fatal exceptions that I was getting was due to the fact that stacks allocated from
     282             the workspace is not necessarily page-aligned and changing their attributes causes exceptions.
     283           * Once I resolved this, I worked on improving the previous patch.
     284           * I was able to write tests for stack isolating and stack-sharing. After I have resolved all the formatting problems,
     285             I will be sending in my improved patches along with the tests for review today.
     286      * ''Blockers:''
     287           *  None as of yet.
     288      * ''Goals for this week:''
     289           * Work on providing a better configuration scheme for thread_stack protection. Right now, we have to define (USE_THREAD_STACK_PROTECTION)
     290             across multiple files.
     291           * Work on my blog and detail all that has to be done for sharing protected stacks.
     292
     293* '''August 5:''' Tenth Meeting
     294      * ''Progress:''
     295           * I was finally able to have a stable working solution for stack isolation and stack sharing.
     296           * Worked on the design problems in my patch, integrated the stack protection attributes to the existing structures.
     297             I will be sending v3 today.
     298           * Tried out the new build system and tried to understand its internals for resolving the configuration issues.
     299      * ''Blockers:''
     300           * Some of the internals of the build system, especially how to use the build specification items to configure isolated
     301             threads is still not clear to me. I will give it another go before asking for help on ml.
     302      * ''Goals for this week:''
     303           * My primary objective this week is to decide and work on the configuration option.
     304           * If this is resolved early, I would start working on providing support for thread_stack isolating for an MPU based system (RISC-V).
     305
     306* '''August 12:''' Eleventh Meeting
     307      * ''Progress:''
     308           * Decided on the configuration mechanism and implemented it using the new build system.
     309           * Resolved all of the issues with the high-level design and tested it with the new build system configuration option.
     310           * Looked into the work that needs to be done for providing RISC-V based MPU suppport.
     311      * ''Blockers:''
     312           * There are a few limitations in my design -
     313               * Whenever context-switch takes place from an interrupt, I get fatal errors.
     314               * At times when the thread acquires a mutex for a critical section I get INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT fatal code.
     315                 I will discuss more about this on the mailing list.
     316      * ''Goals for this week:''
     317           * Blocker resolution.
     318           * Implement static initialization of the RISC-V MPU( PMP ) system.
    281319
    282320