From: Paolo Bonzini <pbonzini@redhat.com>
To: David Hildenbrand <david@redhat.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
Igor Mammedov <imammedo@redhat.com>,
xuyandong <xuyandong2@huawei.com>
Cc: Zhanghailiang <zhang.zhanghailiang@huawei.com>,
"wangxin (U)" <wangxinxin.wang@huawei.com>,
lidonglin <lidonglin@huawei.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Huangweidong (C)" <weidong.huang@huawei.com>
Subject: Re: [Qemu-devel] An emulation failure occurs, if I hotplug vcpus immediately after the VM start
Date: Thu, 7 Jun 2018 13:02:51 +0200 [thread overview]
Message-ID: <e2e0ff2b-139e-0582-c8f9-9a716780ff1f@redhat.com> (raw)
In-Reply-To: <77604174-3c15-a8d3-3ea3-53a1759cd885@redhat.com>
On 07/06/2018 12:37, David Hildenbrand wrote:
>
> I have a related requirement, which would be to atomically grow a
> memory regions. So instead of region_del(old)+region_add(new), I would
> have to do it in one shot (atomically).
>
> AFAICS an atomic replace of the memory map would work for this, too.
> However I am not sure how we want to handle all kinds of tracking data
> that is connected to e.g. x86 memory slots (e.g. rmap, dirty bitmap ...).
The dirty bitmap would be synced in kvm_region_del (so it's not true
that kvm_region_del would disappear, but almost :)).
The rmap is more interesting. Perhaps it can be just rebuilt on every
KVM_SET_USER_MEMORY_REGIONS call.
Paolo
next prev parent reply other threads:[~2018-06-07 11:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 8:17 [Qemu-devel] An emulation failure occurs, if I hotplug vcpus immediately after the VM start xuyandong
2018-06-01 10:23 ` Igor Mammedov
2018-06-06 13:28 ` Gonglei (Arei)
2018-06-06 13:57 ` Paolo Bonzini
2018-06-06 14:18 ` xuyandong
2018-06-06 14:23 ` Paolo Bonzini
2018-06-07 10:37 ` David Hildenbrand
2018-06-07 11:02 ` Paolo Bonzini [this message]
2018-06-07 11:36 ` David Hildenbrand
2018-06-07 12:36 ` Paolo Bonzini
2018-06-07 12:55 ` David Hildenbrand
2018-06-07 16:03 ` 浙大邮箱
2018-06-11 10:44 ` David Hildenbrand
2018-06-11 12:25 ` Gonglei (Arei)
2018-06-11 12:36 ` David Hildenbrand
2018-06-11 13:25 ` Gonglei (Arei)
2018-06-07 10:39 ` David Hildenbrand
2018-06-07 11:13 ` Gonglei (Arei)
2018-06-07 11:43 ` David Hildenbrand
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=e2e0ff2b-139e-0582-c8f9-9a716780ff1f@redhat.com \
--to=pbonzini@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=david@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lidonglin@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.com \
--cc=xuyandong2@huawei.com \
--cc=zhang.zhanghailiang@huawei.com \
/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).