From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PULL] Removal of cpu_register_io_memory
Date: Mon, 12 Mar 2012 16:08:56 +0200 [thread overview]
Message-ID: <4F5E0378.9080705@redhat.com> (raw)
The memory core now has double indirection during dma or kvm I/O
dispatch: first we lookup a MemoryRegionSection from the memory page
table, then we look up the ram_addr to dispatch the I/O operation.
This patchset eliminates the second lookup. To do that, we now store a
MemoryRegionSection index in the iotlb instead of a ram_addr.
The patches were posted on the list a few days ago and received no
negative (or positive) review, and testing with the qemu images seems to
work fine.
Please pull from:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/core
----------------------------------------------------------------
Avi Kivity (5):
memory: make phys_page_find() return an unadjusted section
memory: store section indices in iotlb instead of io indices
exec: fix code tlb entry misused as iotlb in get_page_addr_code()
memory: dispatch directly via MemoryRegion
memory: get rid of cpu_register_io_memory()
cpu-all.h | 8 -
exec-all.h | 9 +-
exec-obsolete.h | 3 -
exec.c | 362
++++++++++++++++++++--------------------------------
memory.c | 13 +-
softmmu_template.h | 40 +++---
6 files changed, 168 insertions(+), 267 deletions(-)
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2012-03-12 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 14:08 Avi Kivity [this message]
2012-03-13 2:22 ` [Qemu-devel] [PULL] Removal of cpu_register_io_memory 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=4F5E0378.9080705@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.