Success criteria

Multicore interference tests typically check a wide variety of properties of the software, not only checking timing results, but also validating that expected results from hardware event monitors are observed during testing.

With RVS, you can define custom success criteria to perfectly match your expected test results. 

For example, if you're observing the impact of interference due to resource contention on the L1 cache, you may want to specify the following success criteria:

• L1 cache activity for the software is within expected range
• L1 cache activity for the software during resource contention is still within expected range
• Resource partitioning is performing within expected parameters (i.e. your interference generator slows down but your software doesn't/resource access patterns change for one but not the other)  

After defining your success criteria in the multicore test format and collecting your results, results are displayed in the RVS Project Manager and can be exported to provide certification evidence.