Ryan Neph d93be8c65f vm_control: enable fixed_blob_mapping + noncoherent-dma ... Certain platforms use the noncoherent-dma feature to appropriately consider the guest PAT's memory type (caching mode) when configuring the effective memory type in SLAT, instead of simply ignoring it in favor of the host PAT. Dynamic blob mapping has already integrated support for noncoherent-dma upon setting up each mapped blob's memory region (e.g. KVM memslot), but fixed_blob_mapping merged while naively ignoring the feature. Now, we respect the feature when setting up the shared/prepared memory region (appropriately passing the new MemCacheType enum through to the hypervisor). BUG=b:246334944 TEST=tools/presubmit TEST=(in venus-enabled VM w/ noncoherent-dma) `deqp-vk -n dEQP-VK.memory*` passing TEST=(in venus-enabled VM w/ noncoherent-dma) Hollow Knight, Portal 2, Valheim, CS:Source all look fine. Change-Id: Ia31763c80765a42a1932bfb347ffa57a2faf6fab Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5285309 Commit-Queue: Ryan Neph <ryanneph@google.com> Reviewed-by: Yiwei Zhang <zzyiwei@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>		2024-02-16 00:09:55 +00:00
..
src	vm_control: enable fixed_blob_mapping + noncoherent-dma	2024-02-16 00:09:55 +00:00
tests/irqchip	hypervisor: stop restoring TSC offset snapshot.	2023-11-22 23:04:24 +00:00
Cargo.toml	Cargo.toml: add noncoherent-dma feature flag	2024-01-26 23:27:58 +00:00