Feature #13932
closed
improve bhyve second level page table support
100%
Description
As part of the march towards supporting live migration in bhyve, we would like improve support for the handling of hardware-defined nested page tables. There's nothing wrong with the code that is there now per se, but it would be nice to have an accounting structure that more closely matched the shape of the second level paging radix tree, and that supports walking the nested page table by directly access the hardware page table structures.
Related issues
Updated by Dan Cross over 1 year ago
- Related to Feature #13862: EPT/RVI supports resetting A/D bits added
Updated by Dan Cross over 1 year ago
For testing: we booted kernels with this code on both AMD and Intel hosts and booted VMs running Linux and Windows, where we observed that the system remained stable and performant.
Additionally, I built a testing shim that allowed me to exercise the new code from userspace, letting me make assertions against the new interfaces and validate that they behaved as expected, dump the radix tree, etc. Unfortunately, the shim itself is a bit messy, so that code is not included here.
Updated by Dan Cross over 1 year ago
Also, `findleaks` on a kernel dump and saw no unexpected[*] leaks (* ACPICA is known to "leak" RAM which findleaks sees).
Updated by Electric Monk over 1 year ago
- Status changed from New to Closed
- % Done changed from 0 to 100
git commit b4ceea05088ba1b5fae1914544a808623516aa80
commit b4ceea05088ba1b5fae1914544a808623516aa80
Author: Dan Cross <cross@oxidecomputer.com>
Date: 2021-07-26T18:16:10.000Z
13932 improve bhyve second level page table support
13862 EPT/RVI supports resetting A/D bits
Reviewed by: Patrick Mooney <pmooney@pfmooney.com>
Reviewed by: C Fraire <cfraire@me.com>
Reviewed by: Adam Leventhal <adam.leventhal@gmail.com>
Approved by: Dan McDonald <danmcd@joyent.com>
Updated by Patrick Mooney over 1 year ago
- Related to Bug #13981: bhyve emulation should set dirty bits added
Updated by Patrick Mooney over 1 year ago
- Related to Bug #14042: GPT: Closed ranges conflict with other code causing panics added