首页> 外文会议>IEEE/AIAA 29th Digital Avionics Systems Conference >On-the-fly healing of race conditions in ARINC-653 flight software
【24h】

On-the-fly healing of race conditions in ARINC-653 flight software

机译:ARINC-653飞行软件中飞行状况的实时修复

获取原文

摘要

The ARINC-653 standard architecture for flight software specifies an application executive (APEX) which provides an application programming interface and defines a hierarchical framework which provides health management for error detection and recovery. In every partition of the architecture, however, asynchronously concurrent processes or threads may include concurrency bugs such as unintended race conditions which are common and difficult to remove by testing. A race condition toward a shared data, or data race, is a pair of unsynchronized instructions that access a shared variable with at least one write access. Data races threaten the reliability of shared-memory programs seriously and latently, because they result in unintended nondeterministic executions of the programs. To heal data race during executions of ARINC-653 flight software, this paper instruments on-the-fly race detection into the target program and incorporates on-the-fly race healing into the health management of the ARINC-653 architecture. The race detection signals to the health monitor using the corresponding APEX call, if a data race is detected. The health monitor then responds by invoking an aperiodic, user-defined, error handling process that is assigned the highest possible priority. This special process uses an APEX call to identify and then heals the occurrence of race condition as an application error, one of seven error types defined by ARINC-653. This race-healing process allows the target programs to be assured at run-time that the execution result of the healed program could have been in the original program and therefore no new functional bug has been introduced. This paper evaluates efficiencies of the on-the-fly mechanisms to argue that they are practical to be configured under the ARINC-653 partitions.
机译:飞行软件的ARINC-653标准体系结构指定了一个应用执行程序(APEX),它提供了一个应用程序编程接口,并定义了一个层次结构的框架,该框架提供了用于错误检测和恢复的健康管理。但是,在体系结构的每个分区中,异步并发进程或线程可能包括并发错误,例如意外的竞争条件,这些并发错误很常见,并且很难通过测试消除。对共享数据的争用条件或数据争用是一对不同步的指令,它们以至少一个写访问权访问共享变量。数据争用严重且潜在地威胁着共享内存程序的可靠性,因为它们会导致程序的意外的不确定性执行。为了在ARINC-653飞行软件执行过程中修复数据争用,本文将飞行中的种族检测功能检测到目标程序中,并将飞行中的种族恢复功能整合到ARINC-653体系结构的健康管理中。如果检测到数据争用,则争用检测将使用相应的APEX呼叫向运行状况监视器发出信号。然后,运行状况监视程序将通过调用一个非周期性的,用户定义的,错误处理过程进行响应,该过程被分配了最高优先级。这个特殊过程使用APEX调用来识别竞争状况的发生,然后将其作为应用程序错误加以修复,这是ARINC-653定义的七种错误类型之一。通过这种种族修复过程,可以在运行时确保目标程序的执行结果可以在原始程序中,因此不会引入新的功能错误。本文评估了动态机制的效率,认为它们可以在ARINC-653分区下进行配置。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号