FuSa SIG/Status: Difference between revisions

From Xen
Jump to navigationJump to search
(Created page with "= Ongoing Efforts = * Requirements format (doxygen) * Misra requirement classification ** table of requirements followed/to be followed/not applicable ** doorstop (links req...")
 
No edit summary
Line 1: Line 1:
= Scope Definition =
* Hardware
** 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 (a certifiable VM and a non-certifiable VM)

= Ongoing Efforts =
= Ongoing Efforts =


Line 4: Line 15:


* Misra requirement classification
* Misra requirement classification
** table of requirements followed/to be followed/not applicable
** table of requirements followed/to be followed/not applicable
** doorstop (links requirements to code)
** doorstop (links requirements to code)
** Zephyr solution (originally by Intel) based on doxygen
** Zephyr solution (originally by Intel) based on doxygen


* static code analysis (cppcheck, Coverity, Eclair)
* static code analysis (cppcheck, Coverity, Eclair)
** goal: Misra code compliance
** goal: Misra code compliance


* Real-time and interference reduction
* Real-time and interference reduction
** real time analysis of Xen
** real time analysis of Xen
*** interrupt forward response time
*** interrupt forward response time
** cache coloring
** cache coloring


* commit review tracing
* commit review tracing
** get info from mailing list archive
** get info from mailing list archive


* static system definition
* static system definition
** static memory allocation
** static memory allocation
** static heap allocation
** static heap allocation
** cpupools
** cpupools


[[Category:Safety Certification/FuSa SIG]]
[[Category:Safety Certification/FuSa SIG]]

Revision as of 01:53, 15 March 2022

Scope Definition

  • Hardware
    • 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 (a certifiable VM and a non-certifiable VM)

Ongoing Efforts

  • Requirements format (doxygen)
  • Misra requirement classification
    • table of requirements followed/to be followed/not applicable
    • doorstop (links requirements to code)
    • Zephyr solution (originally by Intel) based on doxygen
  • static code analysis (cppcheck, Coverity, Eclair)
    • goal: Misra code compliance
  • Real-time and interference reduction
    • real time analysis of Xen
      • interrupt forward response time
    • cache coloring
  • commit review tracing
    • get info from mailing list archive
  • static system definition
    • static memory allocation
    • static heap allocation
    • cpupools