RFC KVM: x86: honor guest memory type
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 28 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | KVM: vmx: rewrite the comment in vmx_get_mt_maskarch/ | +17 | 1 reply | |
| 2/3 | RFC: KVM: add KVM_MEM_DMADocumentation/ include/ virt/ | +18 | 0 replies | |
| 3/3 | RFC: KVM: x86: support KVM_CAP_DMA_MEMarch/ arch/ | +7 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/3] KVM: x86: honor guest memory type
Hi,
Host GPU drivers like to give userspace WC mapping. When the userspace makes the mapping available to a guest, it also tells the guest to create a WC mapping. However, even when the guest kernel picks the correct memory type, it gets ignored because of VMX_EPT_IPAT_BIT on Intel.
This series adds a new flag to KVM_SET_USER_MEMORY_REGION, which tells the host kernel to honor the guest memory type for the memslot. An alternative fix is for KVM to unconditionally honor the guest memory type (unless it is MMIO, to avoid MCEs on Intel). I believe the alternative fix is how things are on ARM, and probably also how things are on AMD.
I am new to KVM and HW virtualization technologies. This series is meant as an RFC.
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel