目的与范围
用途与范围
本单元实现 PTO v0 的系统寄存器访问控制规则。它判断给定 AccessControlRing 是否允许读取或写入某个 SystemRegisterAddress。
PTO-ARCH-PROFILE-APPLICABILITY下面直接显示完整的 ASL 所有者。
// PTO-UNIT: {"id":"PTO-ARCH-PROFILE-APPLICABILITY","surface":"arch","classification":["profile","applicability"],"depends_on":["PTO-ARCH-PROFILE-RESET"]}readonly implementation func SystemRegisterAccessPermitted( address: SystemRegisterAddress, write: boolean, ring: AccessControlRing) => booleanbegin // Base registers are available at every level. Context, translation, and // debug register families are ACR0-only in the PTO v0 profile. return UInt(address[11:0]) < 0x0f00 || ring == 0;end;
本单元实现 PTO v0 的系统寄存器访问控制规则。它判断给定 AccessControlRing 是否允许读取或写入某个 SystemRegisterAddress。
address、write 标志以及当前 ring。12 位和 ACR 层级编号。0x0f00 的地址;上下文、地址转换和调试寄存器族从该边界开始。当地址低 12 位小于 0x0f00 时,SystemRegisterAccessPermitted 返回真。达到或超过 0x0f00 时,只有 ring == 0 才返回真。当前实现对读取与写入使用同一边界。
这是 PTO v0 参考配置档的 implementation 函数。它并不承诺每个未来具名配置档都采用相同地址分界或权限规则。
本示例块只用于帮助阅读:先应用上文规则,再到规范 ASL 所有者中确认结果。它不会增加任何架构契约。
正文来自 owning ASL。拖拽或按钮只临时改变当前页面显示顺序。
No NDF clause is attached to this unit.
10 matching entries
PTO-AVS-ARCH-PROFILE-APPLICABILITY-STATIC-001tests/asl/arch/profile/applicability/arch-static-applicability-contract-001.asl72e3606eddaf180815dfda25f6e262401c3e8d840afe5b2e43f4087568c8a87dPTO-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-0005…
ADR-0005docs/status/decisions/0005-pto-v0-concrete-reference-profile.mda83528c2fc744cc120c2a0a32c82410059638ea88936fa65ac0eb36a0274d87cLoading ADR-0037…
ADR-0037docs/status/decisions/0037-numeric-profile-identity-and-variation-framework.mdb09efd36ccfc7258d1743c974f42b875ead42137c503f576a12f471f65b52e30Loading ADR-0042…
ADR-0042docs/status/decisions/0042-numeric-variation-point-ownership.mdf25df23306837e4199f6b7c03f70de853a693fdc6435c65ead57b2a174076081Loading ADR-0049…
ADR-0049docs/status/decisions/0049-hardware-subnormal-policy.mdac969b6247bbaa16e480ae96c9f227f68ffa859d06121df838c8d3b6f141ca3a{
"classification": [
"profile",
"applicability"
],
"documentation": "docs/arch/profile/applicability.md",
"id": "PTO-ARCH-PROFILE-APPLICABILITY",
"mnemonic": null,
"readiness_subjects": [
"ADR-0005",
"ADR-0037",
"ADR-0042",
"ADR-0049"
],
"semantic_tests": [],
"source": "asl/arch/profile/applicability.asl",
"surface": "arch",
"tests": [
"PTO-AVS-ARCH-PROFILE-APPLICABILITY-STATIC-001"
]
}0.58.5 · 候选发布7dc8b7e5b121d2b2499a2273bebff29e2cd86812b3734d16ed92c3e7f9d8a99047009c8b0996cbeb88a087296c12696d9965de412cf3c1353c94f4dfedc2459341c8db37e26f07520c440335e05554bab30daf0easl/arch/profile/applicability.asl