Is there an existing issue for this?
Current Behavior
The current patina_internal_cpu has pre-mature layout, which caused some odd clippy and testing issues.
One example would be the mod x64 from interrupts crate is marked as a private sub-module while some of the contents are marked as public and aliased during re-export. This caused the clippy to go haywire when evaluating these internally public structures.
The same applies to aarch64 side.
Expected Behavior
This combination of public structure and private module model should be untangled. Similar to paging crate, we should be able to guard out only the inline/raw assembly code and pull in the same logic (code) for both aarch64 and x64 for test builds and dead_code mark should be removed when that happens.
Steps To Reproduce
Remove the #[allow(dead_code)] from
Build Environment
- OS(s): Windows
- Tool Chain(s): nightly 2026-02-06
- Targets Impacted: x64 and aarch64.
Version Information
Urgency
Medium
Are you going to fix this?
Someone else needs to fix it
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
Is there an existing issue for this?
Current Behavior
The current patina_internal_cpu has pre-mature layout, which caused some odd clippy and testing issues.
One example would be the
mod x64from interrupts crate is marked as a private sub-module while some of the contents are marked as public and aliased during re-export. This caused the clippy to go haywire when evaluating these internally public structures.The same applies to aarch64 side.
Expected Behavior
This combination of public structure and private module model should be untangled. Similar to paging crate, we should be able to guard out only the inline/raw assembly code and pull in the same logic (code) for both aarch64 and x64 for test builds and
dead_codemark should be removed when that happens.Steps To Reproduce
Remove the
#[allow(dead_code)]fromBuild Environment
Version Information
Urgency
Medium
Are you going to fix this?
Someone else needs to fix it
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response