qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: xuyandong <xuyandong2@huawei.com>,
	"Gonglei (Arei)" <arei.gonglei@huawei.com>,
	Igor Mammedov <imammedo@redhat.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: Wed, 6 Jun 2018 16:23:59 +0200	[thread overview]
Message-ID: <86fe2845-0804-ff48-cf1b-3bf7e4ff3310@redhat.com> (raw)
In-Reply-To: <7CECC2DFC21538489F72729DF5EFB4D9C1D8F1@dggemm501-mbs.china.huawei.com>

On 06/06/2018 16:18, xuyandong wrote:
>> We don't.  It's generally a guest bug if they do, but the problem here is that
>> QEMU is splitting a memory region in two parts and that is not atomic.
>> 	
>> One fix could be to add a KVM_SET_USER_MEMORY_REGIONS ioctl that
>> replaces the entire memory map atomically.
>>
>> Paolo
> After we add a KVM_SET_USER_MEMORY_REGIONS ioctl that replaces the entire
> memory map atomically, how to use it in address_space_update_topology?
> Shall we checkout the spilt memory region before 
> " address_space_update_topology_pass(as, old_view, new_view, false); 
> address_space_update_topology_pass(as, old_view, new_view, true);

You would add the regions to an array in kvm_region_add, and send the
ioctl in the .commit callback of MemoryListener.

kvm_region_del would disappear.  The .commit callback would also look at
the array from the previous execution, and call memory_region_unref on
the regions in there.

Paolo

  reply	other threads:[~2018-06-06 14:24 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 [this message]
2018-06-07 10:37       ` David Hildenbrand
2018-06-07 11:02         ` Paolo Bonzini
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=86fe2845-0804-ff48-cf1b-3bf7e4ff3310@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arei.gonglei@huawei.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).