KVM: handling of MMIO pass-through regions
Get series with b4
b4 am 20140929130745.GF3095@cboxVersions newest first
- v1 Latest6 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | arm/arm64: KVM: use __GFP_ZERO not memset() to get zeroed pages | +0 | 0 replies | |
| 2/6 | arm/arm64: KVM: fix potential NULL dereference in user_mem_abort() | +0 | 0 replies | |
| 2/6 | arm/arm64: KVM: fix potential NULL dereference in user_mem_abort() | +0 | 1 reply | |
| 3/6 | arm/arm64: KVM: add 'writable' parameter to kvm_phys_addr_ioremap | +0 | 1 reply | |
| 3/6 | arm/arm64: KVM: add 'writable' parameter to kvm_phys_addr_ioremap | +0 | 0 replies | |
| 3/6 | arm/arm64: KVM: add 'writable' parameter to kvm_phys_addr_ioremap | +0 | 0 replies | |
| 4/6 | ARM: kvm: define PAGE_S2_DEVICE as read-only by default | +0 | 0 replies | |
| 5/6 | arm64: kvm: define PAGE_S2_DEVICE as read-only by default | +0 | 1 reply | |
| 6/6 | arm/arm64: KVM: map MMIO regions at creation time | +0 | 0 replies |
Reviews trailers per patch
5 of 9 patches have a Reviewed-by or Acked-by.
| Patch | Christoffer Dall | Marc Zyngier |
|---|---|---|
| 1/6 | A-b | |
| 2/6 | A-b | |
| 2/6 | A-b | |
| 3/6 | ||
| 3/6 | ||
| 3/6 | ||
| 4/6 | A-b | |
| 5/6 | A-b | |
| 6/6 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/6] KVM: handling of MMIO pass-through regions
Quoted 23 lines · Ard Biesheuvel
This is a followup to the patches 'kvm: define
PAGE_S2_DEVICEas 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.Patch #4 and #5 were sent out before, and change the value of
PAGE_S2_DEVICEto read-only, so that read-only regions can be ioremap()'edPatch #6 ensures that
VM_PFNMAPlinear mappings of non-system RAM host memory are mapped eagerly rather than faulted in page by page.
Quoted 8 lines
Ard Biesheuvel (6):
arm/arm64: KVM: use__GFP_ZEROnotmemset()to get zeroed pages arm/arm64: KVM: fix potential NULL dereference inuser_mem_abort()arm/arm64: KVM: add 'writable' parameter tokvm_phys_addr_ioremap
ARM: kvm: definePAGE_S2_DEVICEas read-only by default
arm64: kvm: definePAGE_S2_DEVICEas read-only by default arm/arm64: KVM: map MMIO regions at creation time
So I only had comments on that last one and the others are fairly benign and small patches, so assuming the arch maintainers don't complain about the mm header changes, I can queue the first 5 patches and add the last one when we sort that out.
Thanks,
-Christoffer