{'fraction_non_alphanumeric': 0.03505535055350553, 'fraction_numerical': 0.004612546125461255, 'mean_word_length': 5.1647727272727275, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
LiVe: Timely error detection in light-lockstep safety critical systems

Safety-critical systems rely on features such as lockstep execution for error detection, and reset and reexecution for error correction. In particular, light lockstep is an attractive choice since it does not require redesigning cores but, instead, comparing off-core activities (i.e. data/addresses sent). While this approach suffices to guarantee functional correctness of the system, as needed for certification against safety standards (e.g., ISO26262), it fails to provide any timing guarantee as the time elapsed since the error occurs until lockstep detects it can be inordinately large. In this paper (i) we analyse the timing behaviour of errors in light lockstep systems, showing that a significant fraction of errors may remain undetected for long periods. Then, (ii) we put this problem in the context of certification against safety standards. Finally, (iii) we propose LiVe (Lightly Verbose), an approach to guarantee timely detection of errors at low cost in the context of light lockstep systems.