x86: svm: bare-metal fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | x86: svm: clear CR4.DE on DR intercept testx86/ | +1 | 3 replies | |
| 2/4 | x86: svm: present bit is set on nested page-faultsx86/ | +2 | 0 replies | |
| 3/4 | x86: remove blind writes from setup_mmu()lib/ | +0 | 0 replies | |
| 4/4 | x86: Allow to limit maximum RAM addresslib/ lib/ lib/ | +12 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [kvm-unit-tests PATCH 0/4] x86: svm: bare-metal fixes
These patches are intended to allow the svm tests to run on bare-metal. The second patch indicates there is a bug in KVM.
Unfortunately, two tests still fail on bare-metal for reasons that I could not figure out, with my somewhat limited SVM knowledge.
The first failure is "direct NMI while running guest". For some reason the NMI is not delivered. Note that "direct NMI + hlt" and others pass.
The second is npt_rw_pfwalk_check. Even after the relevant fixes, exit_info_2 has a mismatch, when the expected value (of the faulting guest physical address) is 0x641000 and the actual is 0x641208. It might be related to the fact that the physical server has more memory, but I could not reproduce it on a VM with more physical memory.
Nadav Amit (4):
x86: svm: clear CR4.DE on DR intercept test
x86: svm: present bit is set on nested page-faults
x86: remove blind writes from setup_mmu()
x86: Allow to limit maximum RAM address
lib/x86/fwcfg.c | 4 ++++ lib/x86/fwcfg.h | 1 + lib/x86/setup.c | 7 +++++++ lib/x86/vm.c | 3 --- x86/svm_tests.c | 5 +++-- 5 files changed, 15 insertions(+), 5 deletions(-)
Signature · 1 line
2.25.1