| commit | e54c5d7bcc31b2c8c2475e981ea3bae8e4ee1708 | [log] [tgz] |
|---|---|---|
| author | Joshua Seaton <joshuaseaton@fuchsia.infra.roller.google.com> | Fri Jan 24 12:36:42 2025 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jan 24 12:38:43 2025 -0800 |
| tree | a105a3c173cbfd94e73e1372819b91f5f26ad16c | |
| parent | bd10cce13b35eb0d33cc20c7a66e0386f61bf7b8 [diff] |
[roll] Roll fuchsia [kernel][phys] Truncate address range before address space set-up In a previous implementation of kernel.memory-limit-mb support, physboot would destructively forget about memory outside that limit. At that time, two other things were also true: * physboot might still touch forgotten RAM outside of that limit, but that was okay since we would set up the identity map for all or RAM before the truncation; * address space set-up made no allocations that would survive into the kernel However, now kernel.memory-limit-mb support is 'non-destructive' (retaining bookkeeping for all present physical memory) and there are address space allocations that do survive into the kernel (e.g., the kernel's own mapping). This means that the sequencing of truncation after address space set-up is problematic - the allocated root page table could end up past the limit - but also no longer necessary! Accordingly, we just reorder things, ensuring that truncation is the first thing that happens after physical memory bookkeeping is initialized. Original-Fixed: 392079172 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1192902 Original-Revision: 7a47aa5d6fd0aadb86d7ed0da35051bbf6bc9311 GitOrigin-RevId: 7f48ed5df1057d9372eb34a52a70378fb122b9b8 Change-Id: I71847ad84d920e2b45979f2fbb8ddbb05bc5e314
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.