-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Boot mem handling #7039
Merged
Merged
Boot mem handling #7039
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
e7093d0
mk/clang.mk: -Wno-gnu-alignof-expression
jenswi-linaro 72ee353
core: arm64: increase thread stack size for debug
jenswi-linaro e0882e7
core: mm: add vaddr_to_phys()
jenswi-linaro e85425b
core: remove CORE_MEM_TA_RAM
jenswi-linaro b8bc7fb
core: add VCORE_FREE_{PA,SZ,END_PA}
jenswi-linaro 5618fbb
core: mm: allow unmapping VCORE_FREE
jenswi-linaro f8c0a29
core: mm: replace MEM_AREA_TA_RAM
jenswi-linaro 59f1f1e
core: mm: unify secure core and TA memory
jenswi-linaro c0791c6
core: virt: phys_mem_core_alloc() use both pools
jenswi-linaro 80ccdbf
core: arm: core_mmu_v7.c: increase MAX_XLAT_TABLES by 2
jenswi-linaro 9130e5b
core: mm: map memory using requested block size
jenswi-linaro bd3436b
core: arm,pager: make __vcore_init_ro_start follow __vcore_init_rx_end
jenswi-linaro 93973e8
core: mm,pager: map remaining physical memory
jenswi-linaro ba02247
core: add CFG_BOOT_MEM and boot_mem_*() functions
jenswi-linaro baa5de3
core: arm: add boot_cached_mem_end
jenswi-linaro e0baad4
core: arm: enable CFG_BOOT_MEM unconditionally
jenswi-linaro a9fbe20
core: mm: allocate temporary memory map array
jenswi-linaro 5986864
core: initialize guest physical memory early
jenswi-linaro 6945236
core: merge core_mmu_init_phys_mem() and core_mmu_init_virtualization()
jenswi-linaro e10641b
core: arm: add CFG_NS_VIRTUALIZATION boot log
jenswi-linaro File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Asan memory is still referenced with
MEM_AREA_TEE_ASAN
memory area ID whenCFG_WITH_PAGER
is enabled. Won't this switch case need to be supported?MEM_AREA_TEE_RAM
is still used whenCFG_CORE_RWDATA_NOEXEC
is disabled. IS that an issue? Maybe it's a bit inconsistent to enableCFG_MEMTAG
but notCFG_CORE_RWDATA_NOEXEC
.Is is OK here to no more clear memtags for
MEM_AREA_TEE_RAM_RW
andMEM_AREA_NEX_RAM_RW
areas?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need to care about
MEM_AREA_TEE_ASAN
since it's not used with memory tagging enabled.That shouldn't be a problem, everything should be covered by
MEM_AREA_SEC_RAM_OVERALL
nonetheless.The same here, is covered by
MEM_AREA_SEC_RAM_OVERALL
.However, while looking at logs etc to double-check I noticed:
We may have this error in more than one place, see commit f01690c ("core: fix mapping init debug trace") for the
dump_mmap_table()
print. I'll investigate further.