qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: quintela@redhat.com
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 8/9] vmstate: Add preallocation for migrating arrays (VMS_ALLOC flag)
Date: Wed, 25 Jun 2014 13:43:18 +0200	[thread overview]
Message-ID: <53AAB5D6.1030608@suse.de> (raw)
In-Reply-To: <874mz98bd2.fsf@troll.troll>


On 25.06.14 13:41, Juan Quintela wrote:
> Alexander Graf <agraf@suse.de> wrote:
>> On 06/12/2014 05:02 PM, Alexey Kardashevskiy wrote:
>>> On 06/08/2014 09:59 AM, Alexey Kardashevskiy wrote:
>>>> On 06/03/2014 11:19 PM, Alexey Kardashevskiy wrote:
>>>>> On 05/30/2014 07:34 PM, Alexey Kardashevskiy wrote:
>>>>>> There are few helpers already to support array migration. However they all
>>>>>> require the destination side to preallocate arrays before migration which
>>>>>> is not always possible due to unknown array size as it might be some
>>>>>> sort of dynamic state. One of the examples is an array of MSIX-enabled
>>>>>> devices in SPAPR PHB - this array may vary from 0 to 65536 entries and
>>>>>> its size depends on guest's ability to enable MSIX or do PCI hotplug.
>>>>>>
>>>>>> This adds new VMSTATE_VARRAY_STRUCT_ALLOC macro which is pretty similar to
>>>>>> VMSTATE_STRUCT_VARRAY_POINTER_INT32 but it can alloc memory for migratign
>>>>>> array on the destination side.
>>>>>>
>>>>>> This defines VMS_ALLOC flag for a field.
>>>>>>
>>>>>> This changes vmstate_base_addr() to do the allocation when receiving
>>>>>> migration.
>>>>>
>>>>> Juan, Peter? No hurry, just pinging in order not to forget :) Thanks!
>>>> Hi, anyone? :)
>>> Ping?
>> Acked-by: Alexander Graf <agraf@suse.de>
> Reviewed-by: Juan Quintela <quintela@redhat.com>
>
> BTW, should I include it, or will it got include through this series?

Thanks a lot for the review :). I'll pick it up - the next patch depends 
on it and we're getting very close to hard freeze.


Alex

  reply	other threads:[~2014-06-25 11:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1401442460-32648-1-git-send-email-aik@ozlabs.ru>
     [not found] ` <1401442460-32648-9-git-send-email-aik@ozlabs.ru>
2014-06-03 13:19   ` [Qemu-devel] [PATCH v3 8/9] vmstate: Add preallocation for migrating arrays (VMS_ALLOC flag) Alexey Kardashevskiy
2014-06-07 23:59     ` Alexey Kardashevskiy
2014-06-12 15:02       ` Alexey Kardashevskiy
2014-06-12 16:57         ` Alexander Graf
2014-06-19 13:56           ` Alexey Kardashevskiy
2014-06-25 11:41           ` Juan Quintela
2014-06-25 11:43             ` Alexander Graf [this message]
     [not found] ` <1401442460-32648-10-git-send-email-aik@ozlabs.ru>
     [not found]   ` <53885895.9090200@suse.de>
     [not found]     ` <53888973.6010909@ozlabs.ru>
     [not found]       ` <53888B8D.1010507@suse.de>
2014-06-25  0:20         ` [Qemu-devel] [PATCH v3 9/9] spapr_pci: Use XICS interrupt allocator and do not cache interrupts in PHB Alexey Kardashevskiy
2014-06-25 11:43 ` [Qemu-devel] [PATCH v3 0/9] Move interrupts from spapr to xics Alexander Graf

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=53AAB5D6.1030608@suse.de \
    --to=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=quintela@redhat.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).