From: Anthony Liguori <anthony@codemonkey.ws>
To: quintela@redhat.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 07/11] eeprom93xx: Use the new hack macro to avoid duplicate field names
Date: Wed, 23 Mar 2011 07:34:00 -0500 [thread overview]
Message-ID: <4D89E8B8.6010404@codemonkey.ws> (raw)
In-Reply-To: <m3ei5ygnv7.fsf@neno.mitica>
On 03/23/2011 04:58 AM, Juan Quintela wrote:
> Anthony Liguori<aliguori@us.ibm.com> wrote:
>> I don't fully understand this hack business but we need field to be unique so..
>>
>> Signed-off-by: Anthony Liguori<aliguori@us.ibm.com>
>> ---
>> hw/eeprom93xx.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/hw/eeprom93xx.c b/hw/eeprom93xx.c
>> index cfa695d..f1d75ec 100644
>> --- a/hw/eeprom93xx.c
>> +++ b/hw/eeprom93xx.c
>> @@ -114,7 +114,7 @@ static const VMStateInfo vmstate_hack_uint16_from_uint8 = {
>> };
>>
>> #define VMSTATE_UINT16_HACK_TEST(_f, _s, _t) \
>> - VMSTATE_SINGLE_TEST(_f, _s, _t, 0, vmstate_hack_uint16_from_uint8, uint16_t)
>> + VMSTATE_SINGLE_TEST_HACK(_f, _s, _t, 0, vmstate_hack_uint16_from_uint8, uint16_t)
>>
>> static bool is_old_eeprom_version(void *opaque, int version_id)
>> {
> After the fact, we need to promote it as "full types".
>
> Basically it is needed when we sent a field with a different size that
> we use it on the struct.
>
> if we have
>
> struct FOOState {
> int32_t bar;
> ....
> }
>
> and it is sent as
>
> VMSTATE_INT8(bar, ....)
>
> In this case, I went through the whole device, checed that int8_t was
> enough and did the change.
>
> But if we have:
>
> struct FOOState {
> int8_t bar;
> ....
> }
>
> and it is sent as
>
> VMSTATE_INT32(bar, ....)
>
> Then it is not trivial :-(
>
> We change FOOState to int32 or we break migration format. Here is where
> the _HACK suffix appeared.
>
> I thought it was not going to be needed a lot, but there are several
> devices that just sent everything over the wire as uint32, independently
> of its type.
Could we get away with just doing:
VMSTATE_UNUSED(3),
VMSTATE_UINT8(bar, ...),
That's fully compatible on the wire and seems to be a clearer expression
of exactly what the problem is.
Regards,
Anthony Liguori
> Later, Juan.
>
next prev parent reply other threads:[~2011-03-23 12:34 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 0:16 [Qemu-devel] [PATCH 00/11] Add live migration unit tests Anthony Liguori
2011-03-23 0:16 ` [Qemu-devel] [PATCH 01/11] Add hard build dependency on glib Anthony Liguori
2011-03-23 8:13 ` Stefan Hajnoczi
2011-03-23 8:19 ` Roy Tam
2011-03-23 8:41 ` Stefan Hajnoczi
2011-03-23 8:58 ` Roy Tam
2011-03-23 9:19 ` [Qemu-devel] " Paolo Bonzini
2011-03-23 9:22 ` [Qemu-devel] " Stefan Hajnoczi
2011-03-23 0:16 ` [Qemu-devel] [PATCH 02/11] vmstate: register all VMStateDescriptions Anthony Liguori
2011-03-23 9:00 ` Alon Levy
2011-03-23 12:30 ` Peter Maydell
2011-03-23 12:37 ` Anthony Liguori
2011-03-23 0:16 ` [Qemu-devel] [PATCH 03/11] vmstate: for vmstate types that reuse the same field, make sure name is unique Anthony Liguori
2011-03-23 2:29 ` Anthony Liguori
2011-03-23 0:16 ` [Qemu-devel] [PATCH 04/11] sb16: fix migration quirk Anthony Liguori
2011-03-23 9:51 ` [Qemu-devel] " Juan Quintela
2011-03-23 12:16 ` Anthony Liguori
2011-03-23 0:16 ` [Qemu-devel] [PATCH 05/11] vga-isa: fix migration by breaking it Anthony Liguori
2011-03-23 9:54 ` [Qemu-devel] " Juan Quintela
2011-03-23 0:16 ` [Qemu-devel] [PATCH 06/11] fdc: fix migration of non-ISA fdc devices Anthony Liguori
2011-03-23 0:16 ` [Qemu-devel] [PATCH 07/11] eeprom93xx: Use the new hack macro to avoid duplicate field names Anthony Liguori
2011-03-23 9:58 ` [Qemu-devel] " Juan Quintela
2011-03-23 12:34 ` Anthony Liguori [this message]
2011-03-23 14:14 ` Juan Quintela
2011-03-23 14:33 ` Anthony Liguori
2011-03-23 0:16 ` [Qemu-devel] [PATCH 08/11] fw_cfg: make sure all VMState fields are unique Anthony Liguori
2011-03-23 0:16 ` [Qemu-devel] [PATCH 09/11] pckbd: make non-ISA pckbd use a unique name Anthony Liguori
2011-03-23 0:16 ` [Qemu-devel] [PATCH 10/11] vl: add a new -vmstate-dump option to write a VMState JSON schema Anthony Liguori
2011-03-23 0:16 ` [Qemu-devel] [PATCH 11/11] test-vmstate: add test case to verify we don't change VMState Anthony Liguori
2011-03-23 2:31 ` Anthony Liguori
2011-03-23 8:37 ` Stefan Hajnoczi
2011-03-23 10:22 ` Peter Maydell
2011-03-23 12:42 ` Anthony Liguori
2011-03-23 14:17 ` [Qemu-devel] " Juan Quintela
2011-03-23 14:52 ` Anthony Liguori
2011-03-23 15:00 ` Peter Maydell
2011-03-23 15:06 ` Jan Kiszka
2011-03-23 16:27 ` Anthony Liguori
2011-03-23 16:36 ` Jan Kiszka
2011-03-23 18:42 ` Anthony Liguori
2011-03-23 16:45 ` Peter Maydell
2011-03-23 17:01 ` Anthony Liguori
2011-03-23 15:26 ` Juan Quintela
2011-03-23 16:14 ` Anthony Liguori
2011-03-23 16:44 ` Juan Quintela
2011-03-23 14:19 ` Juan Quintela
2011-03-23 14:36 ` Peter Maydell
2011-03-23 15:13 ` Juan Quintela
2011-03-23 15:24 ` Peter Maydell
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=4D89E8B8.6010404@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.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).