qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: arei.gonglei@huawei.com, mst@redhat.com, famz@redhat.com,
	marcandre.lureau@redhat.com
Subject: [Qemu-devel] [PATCH 0/4] More cleanups for RAMBlock/ram_addr_t vs. MemoryRegion
Date: Thu, 26 May 2016 10:49:40 +0200	[thread overview]
Message-ID: <1464252584-30832-1-git-send-email-pbonzini@redhat.com> (raw)

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	other threads:[~2016-05-26  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26  8:49 Paolo Bonzini [this message]
2016-05-26  8:49 ` [Qemu-devel] [PATCH 1/4] memory: remove qemu_get_ram_fd, qemu_set_ram_fd, qemu_ram_block_host_ptr Paolo Bonzini
2016-05-26 12:22   ` Marc-André Lureau
2016-05-26 15:37     ` Paolo Bonzini
2016-05-26  8:49 ` [Qemu-devel] [PATCH 2/4] exec: remove ram_addr argument from qemu_ram_block_from_host Paolo Bonzini
2016-05-26 13:19   ` Marc-André Lureau
2016-05-26  8:49 ` [Qemu-devel] [PATCH 3/4] memory: split memory_region_from_host from qemu_ram_addr_from_host Paolo Bonzini
2016-05-26 13:19   ` Marc-André Lureau
2016-05-26  8:49 ` [Qemu-devel] [PATCH 4/4] exec: hide mr->ram_addr from qemu_get_ram_ptr users Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1464252584-30832-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=famz@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).