diff options
| author | Slava Malyugin <slavamn@google.com> | 2018-02-27 17:09:52 -0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2018-02-28 21:30:15 -0800 |
| commit | d1c761354f5d2583763704c8f9a8a7dd61d1dbb7 (patch) | |
| tree | d9126509a9a832bc1eaa445fe0f34c56d70a304a /tests | |
| parent | cd6a187de66ff56948312ae983ca12a12782e774 (diff) | |
| download | crosvm-d1c761354f5d2583763704c8f9a8a7dd61d1dbb7.tar crosvm-d1c761354f5d2583763704c8f9a8a7dd61d1dbb7.tar.gz crosvm-d1c761354f5d2583763704c8f9a8a7dd61d1dbb7.tar.bz2 crosvm-d1c761354f5d2583763704c8f9a8a7dd61d1dbb7.tar.lz crosvm-d1c761354f5d2583763704c8f9a8a7dd61d1dbb7.tar.xz crosvm-d1c761354f5d2583763704c8f9a8a7dd61d1dbb7.tar.zst crosvm-d1c761354f5d2583763704c8f9a8a7dd61d1dbb7.zip | |
crosvm: put devices right after RAM in Guest physical address space
Small core CPUs have limited physical address space, e.g. 16GB. This affects both "real" physical address space as well as "virtual" physical address space implemented by extended page tables. Any page table entry addressing memory beyond physical address limit will produce page fault. The change avoids these faults for memory-mapped devices (e.g. Wayland shared buffers) by moving them next to physical RAM. BUG=none TEST=verified Xwayland boots fine on N3150 (Braswell) Change-Id: I178aa53eb511a98507b2cb28d28ccf422a08b107 Reviewed-on: https://chromium-review.googlesource.com/940191 Commit-Ready: Sonny Rao <sonnyrao@chromium.org> Tested-by: Slava Malyugin <slavamn@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions