Check span placement and stats after every step in huge_page_aware_allocator_fuzz. - #992
Draft
copybara-service[bot] wants to merge 1 commit into
Draft
copybara-service[bot] wants to merge 1 commit into
copybara-service[bot] wants to merge 1 commit into
Conversation
…locator_fuzz. New/NewAligned must return exactly the requested pages, carry the allocator's memory tag, honor the requested power-of-two alignment, and not overlap any live span, tracked in an ordered map keyed by first page. After every top-level instruction, backing stats must account for every live span plus in-flight releases and GetReleaseStats must match the expected totals, rather than only when GatherAndCheckStats or a release instruction happens to run. Record each span's access density so Delete receives the density it was allocated with instead of always kSparse. PiperOrigin-RevId: 983557458
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Check span placement and stats after every step in huge_page_aware_allocator_fuzz.
New/NewAligned must return exactly the requested pages, carry the allocator's
memory tag, honor the requested power-of-two alignment, and not overlap any
live span, tracked in an ordered map keyed by first page. After every
top-level instruction, backing stats must account for every live span plus
in-flight releases and GetReleaseStats must match the expected totals,
rather than only when GatherAndCheckStats or a release instruction happens to
run. Record each span's access density so Delete receives the density it was
allocated with instead of always kSparse.