qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [PATCH 0/4] More cleanups for RAMBlock/ram_addr_t vs. Memor


From: Paolo Bonzini
Subject: [Qemu-devel] [PATCH 0/4] More cleanups for RAMBlock/ram_addr_t vs. MemoryRegion
Date: Thu, 26 May 2016 10:49:40 +0200

This removes some more cases where we unnecessarily go through
ram_addr_t.  Now that MemoryRegions have a RAMBlock pointer, it is
possible to keep reasoning in terms of MemoryRegion+offset everywhere,
except when managing dirty bitmaps and TCG TLB entries.  ram_addr.h
is now included only by cputlb.c, exec.c, kvm-all.c (for dirty bitmaps),
memory.c and migration/ram.c (also for dirty bitmaps).

The diffstat is lying, because some of the insertions actually come
from doc comments. :)

Paolo

Paolo Bonzini (4):
  memory: remove qemu_get_ram_fd, qemu_set_ram_fd,
    qemu_ram_block_host_ptr
  exec: remove ram_addr argument from qemu_ram_block_from_host
  memory: split memory_region_from_host from qemu_ram_addr_from_host
  exec: hide mr->ram_addr from qemu_get_ram_ptr users

 cputlb.c                     |   3 +-
 exec.c                       | 110 +++++++++++++------------------------------
 hw/misc/ivshmem.c            |   5 +-
 hw/virtio/vhost-user.c       |  25 +++++-----
 include/exec/cpu-common.h    |   4 +-
 include/exec/memory.h        |  36 ++++++++++++--
 include/exec/ram_addr.h      |   3 --
 memory.c                     |  39 +++++++++++----
 migration/postcopy-ram.c     |   3 +-
 scripts/dump-guest-memory.py |  19 ++------
 target-i386/kvm.c            |   6 ++-
 11 files changed, 122 insertions(+), 131 deletions(-)

-- 
2.5.5




reply via email to

[Prev in Thread] Current Thread [Next in Thread]