From: "mar.krzeminski" <mar.krzeminski@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
"Krzeminski,
Marcin (Nokia - PL/Wroclaw)" <marcin.krzeminski@nokia.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Alistair Francis <alistair.francis@xilinx.com>,
qemu-arm <qemu-arm@nongnu.org>, Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] hw/arm/virt: vmstate-static-checker.py results
Date: Thu, 18 Aug 2016 21:19:30 +0200 [thread overview]
Message-ID: <e1d7c6a7-969e-283c-0299-10bdc83d3a88@gmail.com> (raw)
In-Reply-To: <CAFEAcA-bnav367B38xcjZt0-TLXh68ZWB3DoJwvu2RT3qRu-Sg@mail.gmail.com>
W dniu 18.08.2016 o 21:05, Peter Maydell pisze:
> On 18 August 2016 at 20:04, Dr. David Alan Gilbert <dgilbert@redhat.com> wrote:
>> Hmm, except there are two separate things with the name "xilinx_spi";
>> vmstate_xilinx_spi in hw/ssi/xilinx_spi.c
>> which is the state for the "xlnx.xps-spi" (aka TYPE_XILINX_SPI) object.
>>
>> and for added confusion:
>> vmstate_m25p80 in hw/block/m25p80.c
>> which is the state for the "m25p80-generic" (aka TYPE_M25P80) object.
>> also calls itself "xilinx_spi".
>>
>> These went in a pair of Peter Crosthwaite commits at about the same time 4.5 years
>> ago; I'm guessing it was just a copy-paste.
>>
>> I think my preference would be to update the name for the m25p80 so it's
>> not got the clash; but it seems m25p80 contains definitions of about a zillion
>> flash devices all derived from the m25p80, so I think I'd have to try one of
>> them to see if the xilinx_spi name finds it's way onto the migration stream;
>> I suspect it doesn't.
> Aha. Yeah, we should fix that. (I have a feeling the m25p80 devices are
> all only for boards where we don't care about migration-compat, but I'm
> not completely certain.)
I had a patch to change vmstate name in m25p80,
but I do not know why I have not send it.
I also believe that there is no board that could use migration of m25p80
devs (yet?).
Regards,
Marcin
>
> thanks
> -- PMM
>
>
prev parent reply other threads:[~2016-08-18 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 14:00 [Qemu-devel] hw/arm/virt: vmstate-static-checker.py results Andrew Jones
2016-08-18 14:06 ` Andrew Jones
2016-08-18 14:26 ` Peter Maydell
2016-08-18 19:04 ` Dr. David Alan Gilbert
2016-08-18 19:05 ` Peter Maydell
2016-08-18 19:19 ` mar.krzeminski [this message]
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=e1d7c6a7-969e-283c-0299-10bdc83d3a88@gmail.com \
--to=mar.krzeminski@gmail.com \
--cc=alistair.francis@xilinx.com \
--cc=amit.shah@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=marcin.krzeminski@nokia.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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).