Skip to content

[Feature]: Define Architectural Interface Location #1452

@os-d

Description

@os-d

Feature Overview

Currently, architectural interfaces (writing architectural registers, io port writing, etc.) are scattered throughout Patina, the SDK, and external crates (x86_64).

Solution Overview

These interfaces should be colocated in the SDK as very thin wrappers around the asm code that does these operations, along with any relevant definitions and structures. Higher level abstractions can then leverage these interfaces to perform whatever actions they need and define an API at the abstraction level. Code that doesn't need an abstraction because it is inherently architecture specific can simply compose the bare wrappers from the SDK however makes sense for their use case.

Alternatives Considered

No response

Urgency

Low

Are you going to implement the feature request?

I will implement the feature

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions