From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, peterx@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] memory: Fix up coalesced_io_del not working for KVM
Date: Tue, 20 Aug 2019 13:16:13 +0800 [thread overview]
Message-ID: <20190820051615.1210-1-peterx@redhat.com> (raw)
v2:
- simply migrate has_coalesced_range in patch 1, while I added
comments in the code because that can be a bit unobvious [Paolo]
v1 is here:
https://lists.gnu.org/archive/html/qemu-devel/2019-08/msg03293.html
Peter Xu (2):
memory: Inherit has_coalesced_range from the same old FlatRange
memory: Split zones when do coalesced_io_del()
memory.c | 39 ++++++++++++++++++++++++++++++++++++---
1 file changed, 36 insertions(+), 3 deletions(-)
--
2.21.0
next reply other threads:[~2019-08-20 5:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 5:16 Peter Xu [this message]
2019-08-20 5:16 ` [Qemu-devel] [PATCH v2 1/2] memory: Inherit has_coalesced_range from the same old FlatRange Peter Xu
2019-08-20 5:16 ` [Qemu-devel] [PATCH v2 2/2] memory: Split zones when do coalesced_io_del() Peter Xu
2019-08-20 6:24 ` Paolo Bonzini
2019-08-20 6:35 ` Peter Xu
2019-08-20 6:37 ` Peter Xu
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=20190820051615.1210-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=pbonzini@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).