ARM异常中断处理详解

版权申诉
0 下载量 135 浏览量 更新于2024-07-07 收藏 183KB PPT 举报
"《异常中断处理》PPT课件.ppt" 本文主要介绍ARM架构下异常中断处理的相关知识,包括异常中断的种类、中断向量表以及异常中断处理的优先级。 异常中断处理是计算机系统中至关重要的部分,它允许系统在运行过程中响应外部事件或者处理内部错误。在ARM体系结构中,异常中断处理机制提供了控制程序执行流程的方式,除了正常的顺序执行和跳转指令,还支持在异常中断发生时自动转移到相应的处理程序。 ARM处理器支持多种类型的异常中断,包括: 1. 复位:当处理器接收到复位信号时,程序跳转到复位异常处理程序执行,用于初始化系统。 2. 未定义指令:当遇到无法识别或处理的指令时,处理器会产生未定义指令异常,常用于软件仿真。 3. 软件中断(SWI):用户模式下执行SWI指令,用于调用特权操作,实现系统功能调用。 4. 指令预取中止:如果预取的指令地址无效或不可访问,会在执行时引发此异常。 5. 数据访问中止:数据读写时,若地址不存在或权限不足,会触发数据中止异常。 6. 外部中断请求(IRQ):当外部设备请求中断,且处理器允许中断时,会进入IRQ异常处理。 7. 快速中断请求(FIQ):比IRQ有更高的优先级,同样用于响应外部设备的快速中断请求。 中断向量表是ARM处理器处理异常中断的关键,它位于内存的低地址端,大小为32字节,每个异常中断占4个字节。这个表中存放的是跳转指令或直接对PC寄存器赋值的指令,用来指明异常发生后程序应跳转到的位置。不同的异常中断有不同的优先级,例如复位具有最高优先级,而数据访问中止的优先级低于预取中止。 异常中断处理的优先级决定了系统如何处理同时发生的多个中断。例如,FIQ具有较高的优先级,可以在处理IRQ之前先响应。中断向量地址与异常中断类型一一对应,每个地址对应一个特定的中断处理程序。中断向量表的组织形式使得系统能够快速定位并执行相应的异常处理代码,确保中断的高效响应。 总结来说,ARM异常中断处理涉及到系统对不同中断类型的识别、中断向量表的使用以及中断处理的优先级管理,这些都是保证系统可靠性和实时性的重要组成部分。了解这些知识对于进行ARM平台的系统设计、驱动开发以及故障排查等工作至关重要。

SELECT PIS.SHOW_FLT_DETAIL AS SHOW_FLT_DETAIL -- new , PIS.SHOW_AWB_DETAIL AS SHOW_AWB_DETAIL -- new , PIS.DISPLAY_AIRLINE_CODE AS CARRIER_CODE , DECODE(PIS.REVERT_FLOW,'N',PIS.FLOW_TYPE,DECODE(PIS.FLOW_TYPE,'I','E','I')) AS FLOW_TYPE , PIS.SHIP_TO_LOCATION AS SHIP_TO_LOCATION , PIS.INVOICE_SEQUENCE AS INVOICE_SEQUENCE , PFT.FLIGHT_DATE AS FLIGHT_DATE , PFT.FLIGHT_CARRIER_CODE AS FLIGHT_CARRIER_CODE , PFT.FLIGHT_SERIAL_NUMBER AS FLIGHT_SERIAL_NUMBER , PFT.FLOW_TYPE AS AIRCRAFT_FLOW , FAST.AIRCRAFT_SERVICE_TYPE AS AIRCRAFT_SERVICE_TYPE , PPT.AWB_NUMBER AS AWB_NUMBER , PPT.WEIGHT AS WEIGHT , PPT.CARGO_HANDLING_OPERATOR AS CARGO_HANDLING_OPERATOR , PPT.SHIPMENT_PACKING_TYPE AS SHIPMENT_PACKING_TYPE , PPT.SHIPMENT_FLOW_TYPE AS SHIPMENT_FLOW_TYPE , PPT.SHIPMENT_BUILD_TYPE AS SHIPMENT_BUILD_TYPE , PPT.SHIPMENT_CARGO_TYPE AS SHIPMENT_CARGO_TYPE , PPT.REVENUE_TYPE AS REVENUE_TYPE , PFT.JV_FLIGHT_CARRIER_CODE AS JV_FLIGHT_CARRIER_CODE , PPT.PORT_TONNAGE_UID AS PORT_TONNAGE_UID , PPT.AWB_UID AS AWB_UID , PIS.INVOICE_SEPARATION_UID AS INVOICE_SEPARATION_UID , PFT.FLIGHT_TONNAGE_UID AS FLIGHT_TONNAGE_UID FROM PN_FLT_TONNAGES PFT , FZ_AIRLINES FA , PN_TONNAGE_FLT_PORTS PTFP , PN_PORT_TONNAGES PPT , FF_AIRCRAFT_SERVICE_TYPES FAST , SR_PN_INVOICE_SEPARATIONS PIS --new , SR_PN_INVOICE_SEP_DETAILS PISD--new , SR_PN_INV_SEP_PORT_TONNAGES PISPT --new WHERE PFT.FLIGHT_OPERATION_DATE >= trunc( CASE :rundate WHEN TO_DATE('01/01/1900', 'DD/MM/YYYY') THEN ADD_MONTHS(SYSDATE,-1) ELSE ADD_MONTHS(:rundate,-1) END, 'MON') AND PFT.FLIGHT_OPERATION_DATE < trunc( CASE :rundate WHEN TO_DATE('01/01/1900', 'DD/MM/YYYY') THEN TRUNC(SYSDATE) ELSE TRUNC(:rundate) END, 'MON') AND PFT.TYPE IN ('C', 'F') AND PFT.RECORD_TYPE = 'M' AND (PFT.TERMINAL_OPERATOR NOT IN ('X', 'A') OR (PFT.TERMINAL_OPERATOR <> 'X' AND FA.CARRIER_CODE IN (SELECT * FROM SPECIAL_HANDLING_AIRLINE) AND PPT.REVENUE_TYPE IN (SELECT * FROM SPECIAL_REVENUE_TYPE) AND PPT.SHIPMENT_FLOW_TYPE IN (SELECT * FROM SPECIAL_SHIPMENT_FLOW_TYPE) AND PFT.FLIGHT_OPERATION_DATE >= (select EFF_DATE from SPECIAL_HANDLING_EFF_DATE) )) AND PFT.DELETING_DATETIME IS NULL AND FA.AIRLINE_UID = PFT.AIRLINE_UID AND FA.DELETING_DATETIME IS NULL AND PTFP.FLIGHT_TONNAGE_UID = PFT.FLIGHT_TONNAGE_UID AND PTFP.RECORD_TYPE = 'M' AND PTFP.DELETING_DATETIME IS NULL AND PPT.TONNAGE_FLIGHT_PORT_UID (+)= PTFP.TONNAGE_FLIGHT_PORT_UID AND PPT.RECORD_TYPE (+)= 'M' AND PPT.DISCREPANCY_TYPE (+)= 'NONE' AND PPT.ADJUSTMENT_INC_FLAG (+)= 'Y' AND PPT.DELETING_DATETIME (+) IS NULL AND FAST.AIRCRAFT_SERVICE_TYPE_UID = PFT.AIRCRAFT_SERVICE_TYPE_UID AND FAST.DELETING_DATETIME IS NULL AND PIS.TEMPORAL_NAME = TO_CHAR((CASE :rundate --new WHEN TO_DATE('01/01/1900', 'DD/MM/YYYY') THEN TRUNC(SYSDATE) ELSE TRUNC(:rundate) END ), 'YYYYMM') || '00' AND PIS.INVOICE_SEPARATION_UID = PISD.INVOICE_SEPARATION_UID --new AND PISD.INVOICE_SEP_DETAIL_UID = PISPT.INVOICE_SEP_DETAIL_UID --new AND PISPT.PORT_TONNAGE_UID = PPT.PORT_TONNAGE_UID --new AND PIS.PRINT_SUPPORTING_DOC = 'Y';上面是oracle的写法,请转成spark SQL的写法。

2023-06-02 上传