FuSa SIG/Roadmap: Difference between revisions
From Xen
				
				
				Jump to navigationJump to search
				
				| No edit summary | No edit summary | ||
| Line 39: | Line 39: | ||
| = Roadmap = | = Roadmap = | ||
| * Fault injection investigation | |||
| * Coverage (gcov and Qemu) | |||
| * MCDC Coverage | |||
| * HW/SW interface investigation | |||
| * Boundary value analysis investigation | |||
| * Zephyr as Dom0 | * Zephyr as Dom0 | ||
| **    tools license issue | **    tools license issue | ||
| Line 58: | Line 63: | ||
| **    process for change requests of reqs | **    process for change requests of reqs | ||
| * Tests | * Tests | ||
| **    coverage | |||
| **    low level testing | **    low level testing | ||
Revision as of 11:25, 3 December 2024
Short term Roadmap and ongoing activities
- Misra compliance
- Done:
- Coverity regular analysis (arm)
- CI internal checks
- Eclair scanning (Bugseng)
- MISRA rules in xen.git (partial) with their status
- MISRA fixes violations
- Coding style
 
- Ongoing:
- MISRA fixes (or reasoning) for few rules
 
 
- Done:
- Requirements and Assumption of use
- Done:
- Created and defined a hierarchy of requirements (Market, Product and Design)
- Generic Timer
- Emulated UART
- Traceability using OpenFastTrace
 
- Ongoing:
- Dom0less domain creation
- Device passthrough
- P2M
 
- To do:
- GICv3, SMMUv3, vGICv3, hyper calls, IOMMU, LAPIC, hypercalls
- a way to trigger updating the rules in case of code changes
 
 
- Done:
- Architecture specifications
- Done:
- Pushed the architecture specs in a branch
 
- To do:
- Upstream the documents in xen.git
 
 
- Done:
- Features
- Ongoing:
- Hyperlaunch
- PCI passthrough
- virtIO and vPCI
- Domain reset
 
- To do:
- vCPU pinning
 
 
- Ongoing:
Roadmap
- Fault injection investigation
- Coverage (gcov and Qemu)
- MCDC Coverage
- HW/SW interface investigation
- Boundary value analysis investigation
- Zephyr as Dom0
- tools license issue
- what functionalities do we actually need ?
 
- Configuration
- per-domain Xen heap static allocation
- configurability (strip down code)
 
- Real-time
- communication LinuxRT - Zephyr
- code improvements
- remove RCU
 
 
- Code quality
- Misra-C compliance
- automatic checks on builds
- check on patches submitted
- include the rules in the coding style
 
- use of a certified compiler
 
- Misra-C compliance
- Documentation and requirements
- process for change requests of reqs
 
- Tests
- low level testing
 

