FuSa SIG/Status

Scope Definition

• Hardware
  • Only platform core components (no platform drivers)
    • timer, mmu, iommu, irq controller
  • board/platform specific code to be done by user

• System configuration
  • Dom0less
  • Mixed criticality (a certifiable VM and a non-certifiable VM)

Ongoing Efforts

• Requirements format (doxygen)
  • table of requirements followed/to be followed/not applicable
  • doorstop (links requirements to code)
  • Zephyr solution (originally by Intel) based on doxygen
  • Challenge: all changes required within 1 release cycle. ACTION: plan out the activities with the committers.

• MISRA C
  • MISRA C working group is evaluating MISRA C rules and accepting them into the Xen coding style.
  • C rules accepted in Xen
  • cppcheck available to detect violations, see *make cppcheck* and *make cppcheck-html*
  • In progress: violations reduction

• static system definition
  • static memory allocation
  • static heap allocation
  • cpupools
  • status: upstraming in progress

• Real-time and interference reduction
  • real time analysis of Xen
    • interrupt forward response time
  • cache coloring
  • status: upstreaming in progress

• commit review tracing
  • get info from mailing list archive
  • script available to retrieve all mailing list discussions from a commit id