QEMU: kvm: cleanup kvm_slot handling
Status from this message: Queued, thanks!
Get series with b4
b4 am [email protected]Versions newest first
Changes in v1 from the cover letter
- minor changes to avoid changing indentation, therefore making it easier to review
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | kvm: require JOIN_MEMORY_REGIONS_WORKSaccel/ | +1 | 0 replies | |
| 2/6 | kvm: factor out alignment of memory sectionaccel/ | +39 | 0 replies | |
| 3/6 | kvm: use start + size for memory rangesaccel/ | +3 | 0 replies | |
| 4/6 | kvm: we never have overlapping slots in kvm_set_phys_mem()accel/ | +11 | 0 replies | |
| 5/6 | kvm: kvm_log_start/stop are only called with known sectionsaccel/ | +12 | 5 replies | |
| 6/6 | kvm: kvm_log_sync() is only called with known memory sectionsaccel/ | +12 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH v1 0/6] QEMU: kvm: cleanup kvm_slot handling
We can heavily simplify the kvm_slot code. Flatview will make sure that we don't have to deal with overlapping slots. E.g. when a memory section is resized, we are first notified about the removal and then about the new memory section.
So basically, we can directly always map one memory section to one kvm slot (if the fixed up size is > 0).
RFC -> v1:
- minor changes to avoid changing indentation, therefore making it easier to review
David Hildenbrand (6):
kvm: require JOIN_MEMORY_REGIONS_WORKS
kvm: factor out alignment of memory section
kvm: use start + size for memory ranges
kvm: we never have overlapping slots in kvm_set_phys_mem()
kvm: kvm_log_start/stop are only called with known sections
kvm: kvm_log_sync() is only called with known memory sections
accel/kvm/kvm-all.c | 235 +++++++++++++++------------------------------------- 1 file changed, 68 insertions(+), 167 deletions(-)
Signature · 1 line
2.13.5