qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC v3 7/8] memory: extend memory_region_add_subregion() to support error reporting
Date: Wed, 8 Jul 2015 19:42:21 +0200	[thread overview]
Message-ID: <559D60FD.7010500@redhat.com> (raw)
In-Reply-To: <20150708165837.62857513@igors-macbook-pro.local>



On 08/07/2015 16:58, Igor Mammedov wrote:
> I'll drop this patch in favor of dedicated
> memory_region_add_subregion_to_hva() API that can fail and return error.

Isn't the deletion of subregion that is done too early for your work?

You don't want the hot-unplug to complete until all the
address_space_unmaps have completed, if I understand correctly.

Paolo

  parent reply	other threads:[~2015-07-08 17:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08  9:46 [Qemu-devel] [RFC v3 0/8] Fix QEMU crash during memory hotplug with vhost=on Igor Mammedov
2015-07-08  9:46 ` [Qemu-devel] [RFC v3 1/8] memory: get rid of memory_region_destructor_ram_from_ptr() Igor Mammedov
2015-07-08  9:46 ` [Qemu-devel] [RFC v3 2/8] memory: introduce MemoryRegion container with reserved HVA range Igor Mammedov
2015-07-08  9:46 ` [Qemu-devel] [RFC v3 3/8] pc: reserve hotpluggable memory range with memory_region_init_hva_range() Igor Mammedov
2015-07-08  9:46 ` [Qemu-devel] [RFC v3 4/8] pc: fix QEMU crashing when more than ~50 memory hotplugged Igor Mammedov
2015-07-08  9:46 ` [Qemu-devel] [RFC v3 5/8] exec: make sure that RAMBlock descriptor won't be leaked Igor Mammedov
2015-07-08  9:46 ` [Qemu-devel] [RFC v3 6/8] exec: add qemu_ram_unmap_hva() API for unmapping memory from HVA area Igor Mammedov
2015-07-08  9:46 ` [Qemu-devel] [RFC v3 7/8] memory: extend memory_region_add_subregion() to support error reporting Igor Mammedov
2015-07-08 11:03   ` Michael S. Tsirkin
2015-07-08 11:09   ` Peter Maydell
2015-07-08 14:58     ` Igor Mammedov
2015-07-08 17:30       ` Michael S. Tsirkin
2015-07-08 18:41         ` Igor Mammedov
2015-07-09  6:58           ` Michael S. Tsirkin
2015-07-08 17:42       ` Paolo Bonzini [this message]
2015-07-08 18:58         ` Igor Mammedov
2015-07-08  9:46 ` [Qemu-devel] [RFC v3 8/8] memory: add support for deleting HVA mapped MemoryRegion Igor Mammedov
2015-07-08  9:58   ` Michael S. Tsirkin
2015-07-08 14:43     ` Igor Mammedov
2015-07-08 14:50       ` Michael S. Tsirkin
2015-07-08 10:01 ` [Qemu-devel] [RFC v3 0/8] Fix QEMU crash during memory hotplug with vhost=on Michael S. Tsirkin
2015-07-08 11:41   ` Igor Mammedov
2015-07-08 11:45     ` Michael S. Tsirkin
2015-07-08 15:46   ` Igor Mammedov
2015-07-09 17:04     ` Andrey Korolyov
2015-07-15 15:18       ` Igor Mammedov
2015-07-15 15:26         ` Andrey Korolyov
2015-07-15 16:08           ` Michael S. Tsirkin
2015-07-15 16:46             ` Andrey Korolyov
2015-07-16 20:35               ` Andrey Korolyov
2015-07-17 20:45                 ` Andrey Korolyov

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=559D60FD.7010500@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).