From: Peter Xu <peterx@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 2/2] memory: Split zones when do coalesced_io_del()
Date: Tue, 20 Aug 2019 14:37:17 +0800 [thread overview]
Message-ID: <20190820063717.GI13560@xz-x1> (raw)
In-Reply-To: <20190820063515.GH13560@xz-x1>
On Tue, Aug 20, 2019 at 02:35:15PM +0800, Peter Xu wrote:
> On Tue, Aug 20, 2019 at 08:24:12AM +0200, Paolo Bonzini wrote:
> > On 20/08/19 07:16, Peter Xu wrote:
> > > It is a workaround of current KVM's KVM_UNREGISTER_COALESCED_MMIO
> > > interface. The kernel interface only allows to unregister an mmio
> > > device with exactly the zone size when registered, or any smaller zone
> > > that is included in the device mmio zone. It does not support the
> > > userspace to specify a very large zone to remove all the small mmio
> > > devices within the zone covered.
> > >
> > > Logically speaking it would be nicer to fix this from KVM side, though
> > > in all cases we still need to coop with old kernels so let's do this.
> > >
> > > This patch has nothing to do with 3ac7d43a6fbb5d4a3 because this is
> > > probably broken from the very beginning when the
> > > KVM_UNREGISTER_COALESCED_MMIO interface is introduced in kernel.
> > > However to make the backport to stables easier, I'm still using the
> > > commit 3ac7d43a6fbb5d4a3 to track this problem because this will
> > > depend on that otherwise even additions of mmio devices won't work.
> > >
> > > Fixes: 3ac7d43a6fbb5d4a3
> > > Signed-off-by: Peter Xu <peterx@redhat.com>
> >
> > What about my comments to this patch? :)
>
> I thought that comment was for patch 1 but wrongly replied to this
> patch 2... :)
>
> Isn't that comment only valid if we still use the old patch 1? With
> your suggestion, is that still needed to keep mr->coalesced untouched?
Oops, ignore this reply... It's needed of course! So it also
affecting this patch...
I'll prepare a v3 soon.
Regards,
--
Peter Xu
prev parent reply other threads:[~2019-08-20 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 5:16 [Qemu-devel] [PATCH v2 0/2] memory: Fix up coalesced_io_del not working for KVM Peter Xu
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 [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=20190820063717.GI13560@xz-x1 \
--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).