Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use new PteFlags to replace old EntryFlags #708

Merged
merged 10 commits into from
Dec 5, 2022

Conversation

kevinaboos
Copy link
Member

No description provided.

@kevinaboos
Copy link
Member Author

cc @NathanRoyer on this since the changes to the memory-related crates may affect your other work & current PRs

@kevinaboos kevinaboos merged commit e7847d5 into theseus-os:theseus_main Dec 5, 2022
@kevinaboos kevinaboos deleted the use_new_pte_flags branch December 5, 2022 07:16
github-actions bot pushed a commit that referenced this pull request Dec 5, 2022
* The `pte_flags` crate offers the following improvements:
  * Builder-style functions to set or clear each flag.
  * A unified interface for checking or setting PTE flags
    across all architectures.
  * The ability to be as generic or as specific to an architecture
    as you like.
  * Lossless conversions from the generic `PteFlags` to the
    arch-specific `PteFlags<Arch>`, and lossy conversions from
    the arch-specific `PteFlags<Arch>` to the generic `PteFlags`.
  * See #699 and #712 for more details.

* All memory mapping functions now accept the PTE flags
  parameter as an instance of `Into<PteFlagsArch>`,
  which allows both arch-generic `PteFlags` and arch-specific
  `PteFlagsX86_64` or `PteFlagsAarch64` to be used. e7847d5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant