目的与范围
用途与范围
FaultCode 是 PTO ASL 为 Fault_None 和 15 个具名且非 None 的故障标识定义的枚举。本单元只定义这些标识,不定义它们何时被选择,也不定义随后发生的状态转换。
PTO-ARCH-DATA-TYPES-FAULT下面直接显示完整的 ASL 所有者。
// PTO-UNIT: {"id":"PTO-ARCH-DATA-TYPES-FAULT","surface":"arch","classification":["data-types","fault"],"depends_on":["PTO-ARCH-DATA-TYPES-INTEGER"]}type FaultCode of enumeration { Fault_None, Fault_ExecutionStateCheck, Fault_IllegalInstruction, Fault_InstructionPC, Fault_InstructionPage, Fault_DataAlignment, Fault_DataPage, Fault_SoftwareBreakpoint, Fault_HardwareBreakpoint, Fault_HardwareWatchpoint, Fault_Assert, Fault_TileLegality, Fault_TileAllocation, Fault_BundleControl, Fault_BundlePostCommit, Fault_ServiceRequest};
FaultCode 是 PTO ASL 为 Fault_None 和 15 个具名且非 None 的故障标识定义的枚举。本单元只定义这些标识,不定义它们何时被选择,也不定义随后发生的状态转换。
Fault_None 表示当前没有故障。执行状态检查、非法指令、指令地址/指令页、数据对齐/数据页、调试、断言、Tile 合法性或分配、指令束控制或提交后故障,以及服务请求,都有各自独立的枚举成员。
这种拆分让后续 ASL 所有者能够选择故障原因,而无需把陷阱号或恢复行为编码进这个类型定义。
一个 FaultCode 值恰好是该枚举的一个成员。这个声明不分配陷阱号、优先级、载荷或恢复行为。
链接到本单元的 AVS 提供跨所有者执行证据,但不属于本页的枚举定义。
Fault_BundleControl 和 Fault_BundlePostCommit 是两个不同的枚举成员。Fault_TileLegality 和 Fault_TileAllocation 也分别是不同成员。
某条指令选择哪个成员,以及陷阱或配置档所有者如何解释该成员,都不属于这个类型声明。
下面只演示阅读路径,不增加故障规则。
当另一个 ASL 单元使用 Fault_DataAlignment 时,应把该单元视为周边行为的所有者;本页只确立 Fault_DataAlignment 是一个独立的 FaultCode 成员。
正文来自 owning ASL。拖拽或按钮只临时改变当前页面显示顺序。
No NDF clause is attached to this unit.
8 matching entries
PTO-AVS-ARCH-DATA-TYPES-FAULT-STATIC-001tests/asl/arch/data-types/fault/arch-static-fault-contract-001.asl09298fe7a9f3232db427f7d0f0b8a64d3cf22fb5374675f2e1a72145d8ef89eePTO-AVS-ARCH-TESTCOMPLETETRAPENVELOPE-FAULT-001tests/asl/arch/data-types/fault/arch-fault-complete-trap-envelope-001.asl7b876a89dc7673cceb61ed326f196fd959295c0173c58ca18ca96b7085b9adcbPTO-EVIDENCE-RELEASE-TRACEABILITYPTO-EVIDENCE-RELEASE-TRACEABILITYspec/evidence/release-traceability-readiness.jsonc7327021d39dc67ac5564bc55073b3870a397d79ac8d9648284d56e33bc14a3ePTO-EVIDENCE-INSTRUCTION-CONTRACT-CLOSUREPTO-EVIDENCE-INSTRUCTION-CONTRACT-CLOSUREspec/evidence/instruction-contract-closure.json3ef2bb62421c79dff8fa77a1c7983923b523244b8090812883ef81286ca8106aPTO-EVIDENCE-ARCHITECTURE-READINESSPTO-EVIDENCE-ARCHITECTURE-READINESSspec/evidence/architecture-readiness.json4b0b85199101251bea744e0f3591cc31906909dc80d5ab651c417a936036a004PTO-EVIDENCE-RELEASE-GATE-READINESSPTO-EVIDENCE-RELEASE-GATE-READINESSspec/evidence/release-gate-readiness.jsona0f4d2b6920c08981ea55fd8ef820708a40d4feb5402c5150e8e9ab532d84ce0PTO-EVIDENCE-RELEASE-MANIFESTPTO-EVIDENCE-RELEASE-MANIFESTspec/release-manifest.json1a64c109ed7a90351c41e2a418b3c0ebaf8ad975838986d2101385186b85c0d8Loading ADR-0018…
ADR-0018docs/status/decisions/0018-pto-v0-trap-disposition.mdce33454ffd2a595425ebece5954c9990ea2b9c4890008ad700599f767d7b9716{
"classification": [
"data-types",
"fault"
],
"documentation": "docs/arch/data-types/fault.md",
"id": "PTO-ARCH-DATA-TYPES-FAULT",
"mnemonic": null,
"readiness_subjects": [
"ADR-0018"
],
"semantic_tests": [
"PTO-AVS-ARCH-TESTCOMPLETETRAPENVELOPE-FAULT-001"
],
"source": "asl/arch/data-types/fault.asl",
"surface": "arch",
"tests": [
"PTO-AVS-ARCH-DATA-TYPES-FAULT-STATIC-001",
"PTO-AVS-ARCH-TESTCOMPLETETRAPENVELOPE-FAULT-001"
]
}0.58.5 · 候选发布7dc8b7e5b121d2b2499a2273bebff29e2cd86812659ed9cbf6286d7011a9156b582b804e5f2e6fa1dd5bd5c3dac70056bd572b9daea74b405567e0fbaff87636bc118020c7676549b47b8dc0ba555acdc6875c13asl/arch/data-types/fault.asl