qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PULL v2] Memory core space reduction
Date: Thu, 01 Mar 2012 14:55:13 +0200	[thread overview]
Message-ID: <4F4F71B1.5000002@redhat.com> (raw)

This is the current memory queue (posted as two separate series before
my vacation).  When applied, the overhead of 16 bytes/page is reduced to
basically nil.

Please pull from:

  git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/core

v2: fix memory corruption in first patch

----------------------------------------------------------------
Avi Kivity (30):
      ioport: change portio_list not to use memory_region_set_offset()
      memory: remove memory_region_set_offset()
      memory: add shorthand for invoking a callback on all listeners
      memory: switch memory listeners to a QTAILQ
      memory: code motion: move MEMORY_LISTENER_CALL()
      memory: move ioeventfd ops to MemoryListener
      memory: add a readonly attribute to MemoryRegionSection
      memory: don't pass ->readable attribute to
cpu_register_physical_memory_log
      memory: use a MemoryListener for core memory map updates too
      memory: drop AddressSpaceOps
      memory: allow MemoryListeners to observe a specific address space
      xen: ignore I/O memory regions
      memory: split memory listener for the two address spaces
      memory: support stateless memory listeners
      memory: change memory registration to rebuild the memory map on
each change
      memory: remove first level of l1_phys_map
      memory: unify phys_map last level with intermediate levels
      memory: store MemoryRegionSection pointers in phys_map
      memory: compress phys_map node pointers to 16 bits
      memory: fix RAM subpages in newly initialized pages
      memory: unify the two branches of cpu_register_physical_memory_log()
      memory: move tlb flush to MemoryListener commit callback
      memory: make phys_page_find() return a MemoryRegionSection
      memory: give phys_page_find() its own tree search loop
      memory: simplify multipage/subpage registration
      memory: replace phys_page_find_alloc() with phys_page_set()
      memory: switch phys_page_set() to a recursive implementation
      memory: change phys_page_set() to set multiple pages
      memory: unify PhysPageEntry::node and ::leaf
      memory: allow phys_map tree paths to terminate early

 exec-obsolete.h |    5 +-
 exec.c          |  875
++++++++++++++++++++++++++++++++++++-------------------
 hw/vhost.c      |   33 ++-
 ioport.c        |   28 ++-
 ioport.h        |    1 +
 kvm-all.c       |   97 ++++++-
 memory.c        |  328 +++++++++-------------
 memory.h        |   26 +-
 xen-all.c       |   33 ++-
 9 files changed, 912 insertions(+), 514 deletions(-)

-- 
error compiling committee.c: too many arguments to function

             reply	other threads:[~2012-03-01 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 12:55 Avi Kivity [this message]
2012-03-02 13:23 ` [Qemu-devel] [PULL v2] Memory core space reduction Anthony Liguori

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=4F4F71B1.5000002@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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).