Skip to content

KVM: handling of MMIO pass-through regions

Christoffer Dall linux-arm-kernel 1 version New

Get series with b4
b4 am 20141010110803.GC3717@cbox

Versions newest first

  1. v1 Latest0 of 6 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 6 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/6] KVM: handling of MMIO pass-through regions
Quoted 15 lines · Ard Biesheuvel

This is a followup to the patches 'kvm: define PAGE_S2_DEVICE as read-only by default' I sent out last week. Essentially build tested
only: while QEMU on KVM still works correctly for my use case with these patches applied, it does not in fact use passthrough mappings of device memory.

Patch #1 is a trivial fix for an issue identified by sparse where we are calling memset(0) on 2 MB worth of pages.

Patch #2 fixes a potential NULL dereference in user_mem_abort()

Patch #3 adds a 'writable' parameter to kmv_phys_addr_ioremap() so that read-only device regions can be mapped using this function. The existing callers are updated to pass 'true' for this parameter.

Quoted 8 lines

Patch #4 and #5 were sent out before, and change the value of PAGE_S2_DEVICE to read-only, so that read-only regions can be ioremap()'ed

Patch #6 ensures that VM_PFNMAP linear mappings of non-system RAM host memory are mapped eagerly rather than faulted in page by page.

Thanks, applied patches 1 through 5 to kvmarm/queue with the fixups discussed.

-Christoffer

Read the cover letter in its thread