From: Halil Pasic <pasic@linux.vnet.ibm.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, Amit Shah <amit.shah@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Guenther Hutzl <hutzl@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC PATCH v2 6/8] migration/vmstate: split up vmstate_base_addr
Date: Fri, 16 Dec 2016 16:57:16 +0100 [thread overview]
Message-ID: <9e79129e-131c-987c-6c13-261be9aee769@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161215132901.GJ2509@work-vm>
On 12/15/2016 02:29 PM, Dr. David Alan Gilbert wrote:
>> + vmstate_handle_alloc(first_elem, field, opaque);
>> + if (field->flags & VMS_POINTER) {
>> + first_elem = *(void **)first_elem;
>> + assert(first_elem);
>> + }
>> for (i = 0; i < n_elems; i++) {
>> void *curr_elem = first_elem + size * i;
>>
>> @@ -310,12 +301,16 @@ void vmstate_save_state(QEMUFile *f, const VMStateDescription *vmsd,
>> while (field->name) {
>> if (!field->field_exists ||
>> field->field_exists(opaque, vmsd->version_id)) {
>> - void *first_elem = vmstate_base_addr(opaque, field, false);
>> + void *first_elem = opaque + field->offset;
>> int i, n_elems = vmstate_n_elems(opaque, field);
>> int size = vmstate_size(opaque, field);
>> int64_t old_offset, written_bytes;
>> QJSON *vmdesc_loop = vmdesc;
>>
>> + if (field->flags & VMS_POINTER) {
>> + first_elem = *(void **)first_elem;
>> + assert(first_elem);
> Can you make that assert(first_elem || !n_elems) please.
> and same above.
>
> Dave
Good catch! This could indeed be some dynamic length
thing with 0 elements.
I'm not sure if I'm going to respin this year though.
Halil
>
>> + }
>> for (i = 0; i < n_elems; i++) {
>> void *curr_elem = first_elem + size * i;
>>
>> --
>> 2.8.4
>>
next prev parent reply other threads:[~2016-12-16 15:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 9:55 [Qemu-devel] [RFC PATCH v2 0/8] VMS_ARRAY_OF_POINTER with null pointers Halil Pasic
2016-11-08 9:55 ` [Qemu-devel] [RFC PATCH v2 1/8] tests/test-vmstate.c: add vBuffer test Halil Pasic
2016-11-08 9:55 ` [Qemu-devel] [RFC PATCH v2 2/8] migration: drop unused VMStateField.start Halil Pasic
2016-11-08 9:55 ` [Qemu-devel] [RFC PATCH v2 3/8] tests/test-vmstate.c: add save_buffer util func Halil Pasic
2016-11-08 9:55 ` [Qemu-devel] [RFC PATCH v2 4/8] tests/test-vmstate.c: add array of pointer to struct Halil Pasic
2016-11-08 9:56 ` [Qemu-devel] [RFC PATCH v2 5/8] migration/vmstate: renames in (load|save)_state Halil Pasic
2016-12-15 11:55 ` Dr. David Alan Gilbert
2016-11-08 9:56 ` [Qemu-devel] [RFC PATCH v2 6/8] migration/vmstate: split up vmstate_base_addr Halil Pasic
2016-12-15 13:29 ` Dr. David Alan Gilbert
2016-12-16 15:57 ` Halil Pasic [this message]
2016-12-16 19:47 ` Dr. David Alan Gilbert
2016-11-08 9:56 ` [Qemu-devel] [RFC PATCH v2 7/8] migration/vmstate: fix array of pointers to struct Halil Pasic
2016-12-15 12:33 ` Dr. David Alan Gilbert
2017-01-31 15:17 ` Halil Pasic
2017-02-01 18:18 ` Dr. David Alan Gilbert
2016-11-08 9:56 ` [Qemu-devel] [RFC PATCH v2 8/8] tests/test-vmstate.c: add array of pointers to struct with NULL Halil Pasic
2016-12-15 12:52 ` Dr. David Alan Gilbert
2016-12-15 13:31 ` [Qemu-devel] [RFC PATCH v2 0/8] VMS_ARRAY_OF_POINTER with null pointers Dr. David Alan Gilbert
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=9e79129e-131c-987c-6c13-261be9aee769@linux.vnet.ibm.com \
--to=pasic@linux.vnet.ibm.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=hutzl@linux.vnet.ibm.com \
--cc=qemu-devel@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).