Minutes Monday Mar 14

[Bertrand Marquis <Bertrand.Marquis@xxxxxxx>]

Current ongoing efforts:
- Requirements format (doxygen)
- Misra requirement classification
    - table of reqs followed/to follow/not applicable
    - doorstop (link requirement to code)
    - Zephyr solution (Intel) based on doxygen
- static code analysis (cppcheck, coverity, eclair)
     - goal: Misra code compliance
- real time analysis of Xen
    - interrupt forward response time
- cache coloring
    - interference free
- commit review tracing
    - get info from mailing list archive
- static system definition
    - static memory allocation
    - static heap allocation
    - cpupools


Misc:
- Scope
    - Only platform core code (no driver)
        - timer, mmu, irq controller
    - board/platform specific code to be done by user of Xen at this stage
    - PCI passthrough out of scope (for now)
- System configuration
    - dom0less
    - Mixed criticality (Cert VM/non cert)


Fusa Roadmap (brainstorm):
- Zephyr as Dom0
    - tools ? license issue !
    - what functionalities ?
- Configuration
    - Per domain Xen heap static allocation
    - configurability (strip down code)
- Real time
    - communication LinuxRT <-> Zephyr
    - code improvements
        - RCU
        - ???
- Code quality
    - Misra compliance
        - automatic checks on builds
        - check on patches submitted
        - include the rules in the coding style
    - Use of a certified compiler
- Documentation and requirements
    - process for change requests of reqs
- Tests
    - tracability
    - coverage
    - low level testing

Detailed analysis:

* Misra compliance
    - ongoing:
        - coverity regular analysis (arm)
            - CI internal checks
        - cppcheck integration in Xen (arm)
            - cppcheck buggy !!
            - Clang ?
            - gcc sanitizer ?
        - classify the rules we want to support
    - to do:
        - create list of rules and put a file in xen git
            - mention the status on the list ?
            - list the rules already covered by current coding style
        - updating the coding style
        - regular checks on gitlab
        - classify the rules in order of priority
        - fix the misra C issues
        - mention the Misra rule fixed when fixing findings
    - for the future
        - submitted patch checks