Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

cleanup/follow-up: memory_map#1240

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
nicholasbishop merged 6 commits intorust-osdev:mainfromphip1611:mem-follow-up
Jul 27, 2024

Conversation

phip1611
Copy link
Member

@phip1611phip1611 commentedJul 14, 2024
edited
Loading

This is a follow-up to our recent additions to the memory map. This ensures a good maintainability in the future.

Changes

IMHO, multiple smaller modules are a better replacement for the gigantic module.

Steps to undraft

Checklist

  • Sensible git history (for example, squash "typo" or "fix" commits). See theRewriting History guide for help.
  • Update the changelog (if necessary)

@phip1611phip1611 self-assigned thisJul 14, 2024
@phip1611phip1611 changed the titlecleanup followup memDraft: cleanup followup memJul 14, 2024
@phip1611phip1611 marked this pull request as draftJuly 14, 2024 07:46
@phip1611phip1611 marked this pull request as ready for reviewJuly 15, 2024 08:50
@phip1611phip1611 changed the titleDraft: cleanup followup memcleanup followup memJul 15, 2024
@nicholasbishop
Copy link
Member

Definitely agree that splitting out some smaller modules is good.

A couple naming thoughts:

  • How aboutmemory_map or justmemory instead ofmmap? Otherwise it sounds likemmap(2)
  • Maybe move it up to a top-level module likeuefi::memory. Although the memory map is retrieved with a boot-services function, it continues to be relevant after exiting boot services, so thematically I think it makes sense at the top level.

@phip1611phip1611force-pushed themem-follow-up branch 2 times, most recently fromb03335a tocfc6b2eCompareJuly 27, 2024 10:31
@phip1611phip1611 changed the titlecleanup followup memcleanup/follow-up: memory_mapJul 27, 2024
@phip1611
Copy link
MemberAuthor

phip1611 commentedJul 27, 2024
edited
Loading

This is now ready for the second review round,@nicholasbishop

@phip1611phip1611 marked this pull request as draftJuly 27, 2024 10:54
@phip1611phip1611 marked this pull request as ready for reviewJuly 27, 2024 12:50
@phip1611phip1611force-pushed themem-follow-up branch 3 times, most recently fromc23c1c3 to09a8c42CompareJuly 27, 2024 13:03
phip1611and others added2 commitsJuly 27, 2024 20:22
As deprecated re-exports are unsupported [0], we go the hard way andjust make it a breaking change.Along the way, I reordered some statements in some files to follow our typicalorder of:- pub mod- private mod- pub use- private use[0]rust-lang/rust#30827
@nicholasbishopnicholasbishop added this pull request to themerge queueJul 27, 2024
Merged via the queue intorust-osdev:main with commit479868fJul 27, 2024
12 checks passed
@phip1611phip1611 deleted the mem-follow-up branchJuly 27, 2024 20:21
@phip1611phip1611 mentioned this pull requestDec 16, 2024
1 task
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@nicholasbishopnicholasbishopnicholasbishop approved these changes

Assignees

@phip1611phip1611

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@phip1611@nicholasbishop

[8]ページ先頭

©2009-2025 Movatter.jp