qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	arei.gonglei@huawei.com, peterx@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/7] memory: Clean up MemoryRegion.ram_addr and optimize address_space_translate
Date: Tue,  1 Mar 2016 14:18:17 +0800	[thread overview]
Message-ID: <1456813104-25902-1-git-send-email-famz@redhat.com> (raw)

v2: In the optimization patch, factor out section_covers_addr() and use it.
    [Paolo, Peter]
    Check "ram_block == NULL" in patch 3. [Gonglei]
    Add Gonglei's rev-by in patches 1, 2, 4 and 5.

The first four patches drop ram_addr from MemoryRegion on top of Gonglei's
optimization.

The next patch simplifies qemu_ram_free a bit by passing the RAMBlock pointer.

The last patch speeds up address_space_translate with a cache pointer inside
the AddressSpaceDispatch.

Fam Zheng (7):
  exec: Return RAMBlock pointer from allocating functions
  memory: Move assignment to ram_block to memory_region_init_*
  memory: Implement memory_region_get_ram_addr with mr->ram_block
  memory: Drop MemoryRegion.ram_addr
  exec: Pass RAMBlock pointer to qemu_ram_free
  exec: Factor out section_covers_addr
  exec: Introduce AddressSpaceDispatch.mru_section

 cputlb.c                |   4 +-
 exec.c                  | 106 +++++++++++++++++++++++++-----------------------
 hw/misc/ivshmem.c       |   9 ++--
 include/exec/memory.h   |   9 +---
 include/exec/ram_addr.h |  24 +++++------
 kvm-all.c               |   3 +-
 memory.c                |  56 ++++++++++++++-----------
 7 files changed, 111 insertions(+), 100 deletions(-)

-- 
2.4.3

             reply	other threads:[~2016-03-01  6:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01  6:18 Fam Zheng [this message]
2016-03-01  6:18 ` [Qemu-devel] [PATCH v2 1/7] exec: Return RAMBlock pointer from allocating functions Fam Zheng
2016-03-01  6:18 ` [Qemu-devel] [PATCH v2 2/7] memory: Move assignment to ram_block to memory_region_init_* Fam Zheng
2016-03-01  6:18 ` [Qemu-devel] [PATCH v2 3/7] memory: Implement memory_region_get_ram_addr with mr->ram_block Fam Zheng
2016-03-01  6:58   ` Gonglei (Arei)
2016-03-01  6:18 ` [Qemu-devel] [PATCH v2 4/7] memory: Drop MemoryRegion.ram_addr Fam Zheng
2016-03-07  9:17   ` [Qemu-devel] [PATCH] scripts: Fix dump-guest-memory.py for MemoryRegion.ram_block removal Fam Zheng
2016-03-07  9:37     ` Laszlo Ersek
2016-03-07  9:45       ` Fam Zheng
2016-03-07 10:08         ` Laszlo Ersek
2016-03-07 13:00     ` Paolo Bonzini
2016-03-07 16:35     ` Janosch Frank
2016-03-08  7:54       ` Janosch Frank
2016-03-08  8:54         ` Fam Zheng
2016-03-01  6:18 ` [Qemu-devel] [PATCH v2 5/7] exec: Pass RAMBlock pointer to qemu_ram_free Fam Zheng
2016-03-01  6:18 ` [Qemu-devel] [PATCH v2 6/7] exec: Factor out section_covers_addr Fam Zheng
2016-03-01  7:23   ` Peter Xu
2016-03-01  9:42   ` Paolo Bonzini
2016-03-02  2:24     ` Fam Zheng
2016-03-01  6:18 ` [Qemu-devel] [PATCH v2 7/7] exec: Introduce AddressSpaceDispatch.mru_section Fam Zheng
2016-03-01  9:43 ` [Qemu-devel] [PATCH v2 0/7] memory: Clean up MemoryRegion.ram_addr and optimize address_space_translate Paolo Bonzini
2016-03-07  8:53 ` Laszlo Ersek
2016-03-07  9:04   ` Fam Zheng

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=1456813104-25902-1-git-send-email-famz@redhat.com \
    --to=famz@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@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).