From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: Glauber Costa <gcosta@redhat.com>, kvm@vger.kernel.org
Subject: Re: [RFC 0/9] Memory registration rework
Date: Wed, 13 Aug 2008 09:13:34 -0500 [thread overview]
Message-ID: <48A2EC0E.3060304@us.ibm.com> (raw)
In-Reply-To: <48A2C8D8.90001@qumranet.com>
Avi Kivity wrote:
> Glauber Costa wrote:
>> Hi folks,
>>
>> Note that this is not tested in anything but x86.
>>
>
> Looks good. The current duplication of memory registration is very
> annoying.
Yeah, I really like the way this series turned out. I agree that this
is the right thing to do.
Regards,
Anthony Liguori
prev parent reply other threads:[~2008-08-13 14:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 0:48 [RFC 0/9] Memory registration rework Glauber Costa
2008-08-13 0:48 ` [PATCH 1/9] add debuging facilities to memory registration at libkvm Glauber Costa
2008-08-13 0:48 ` [PATCH 2/9] experimental change to avoid doing the same thing twice Glauber Costa
2008-08-13 0:48 ` [PATCH 3/9] do not use mem_hole anymore Glauber Costa
2008-08-13 0:48 ` [PATCH 4/9] allow intersecting region to be on the boundary Glauber Costa
2008-08-13 0:48 ` [PATCH 5/9] substitute is_allocated_mem with more general is_containing_region Glauber Costa
2008-08-13 0:48 ` [PATCH 6/9] move kvm_cpu_register_memory_area into qemu's Glauber Costa
2008-08-13 0:48 ` [PATCH 7/9] cleanup kvm memory registration Glauber Costa
2008-08-13 0:48 ` [PATCH 8/9] coalesce mmio regions without an explicit call Glauber Costa
2008-08-13 0:48 ` [PATCH 9/9] remove explicit calls to kvm_qemu_register_coalesced_mmio Glauber Costa
2008-08-13 14:11 ` [PATCH 6/9] move kvm_cpu_register_memory_area into qemu's Anthony Liguori
2008-08-13 14:33 ` Glauber Costa
2008-08-13 11:41 ` [PATCH 5/9] substitute is_allocated_mem with more general is_containing_region Avi Kivity
2008-08-13 13:02 ` Glauber Costa
2008-08-13 11:43 ` [RFC 0/9] Memory registration rework Avi Kivity
2008-08-13 14:13 ` Anthony Liguori [this message]
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=48A2EC0E.3060304@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@qumranet.com \
--cc=gcosta@redhat.com \
--cc=kvm@vger.kernel.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.