From: Wei Huang <wei@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Igor Mammedov <imammedo@redhat.com>,
Shannon Zhao <shannon.zhao@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Shannon Zhao <zhaoshenglong@huawei.com>
Subject: Re: [Qemu-trivial] [PATCH 2/2] ARM: PL061: Misc cleaning fields for PL061 device state
Date: Tue, 2 Feb 2016 09:16:21 -0600 [thread overview]
Message-ID: <56B0C845.9080602@redhat.com> (raw)
In-Reply-To: <56B054A8.6020602@msgid.tls.msk.ru>
On 02/02/2016 01:03 AM, Michael Tokarev wrote:
> 01.02.2016 21:01, Peter Maydell wrote:
>> On 1 February 2016 at 17:20, Wei Huang <wei@redhat.com> wrote:
>>> This patch removes float_high field of PL061State, which doesn't seem
>>> to be used anywhere.
> []
>>> @@ -88,7 +87,6 @@ static const VMStateDescription vmstate_pl061 = {
>>> VMSTATE_UINT32(slr, PL061State),
>>> VMSTATE_UINT32(den, PL061State),
>>> VMSTATE_UINT32(cr, PL061State),
>>> - VMSTATE_UINT32(float_high, PL061State),
>>> VMSTATE_UINT32_V(amsel, PL061State, 2),
>>> VMSTATE_END_OF_LIST()
>>
>> This would be a migration compatibility break, so at a minimum
>> you need to bump the vmstate struct versions.
>
> Is it worth the effort to remove this field if it causes
> compatibility break? Maybe keep it around, it doesn't hurt?
It doesn't hurt. So either way is fine. I just happened to find it while
reviewing the code.
> At the very least, we may rename it to "unused_float_high",
> or something, to indicate it is a known-unused?
I don't think renaming solves any problem. Either we keep this variable
as it is or remove it.
>
> Thanks,
>
> /mjt
>
WARNING: multiple messages have this Message-ID (diff)
From: Wei Huang <wei@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Igor Mammedov <imammedo@redhat.com>,
Shannon Zhao <shannon.zhao@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Shannon Zhao <zhaoshenglong@huawei.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] ARM: PL061: Misc cleaning fields for PL061 device state
Date: Tue, 2 Feb 2016 09:16:21 -0600 [thread overview]
Message-ID: <56B0C845.9080602@redhat.com> (raw)
In-Reply-To: <56B054A8.6020602@msgid.tls.msk.ru>
On 02/02/2016 01:03 AM, Michael Tokarev wrote:
> 01.02.2016 21:01, Peter Maydell wrote:
>> On 1 February 2016 at 17:20, Wei Huang <wei@redhat.com> wrote:
>>> This patch removes float_high field of PL061State, which doesn't seem
>>> to be used anywhere.
> []
>>> @@ -88,7 +87,6 @@ static const VMStateDescription vmstate_pl061 = {
>>> VMSTATE_UINT32(slr, PL061State),
>>> VMSTATE_UINT32(den, PL061State),
>>> VMSTATE_UINT32(cr, PL061State),
>>> - VMSTATE_UINT32(float_high, PL061State),
>>> VMSTATE_UINT32_V(amsel, PL061State, 2),
>>> VMSTATE_END_OF_LIST()
>>
>> This would be a migration compatibility break, so at a minimum
>> you need to bump the vmstate struct versions.
>
> Is it worth the effort to remove this field if it causes
> compatibility break? Maybe keep it around, it doesn't hurt?
It doesn't hurt. So either way is fine. I just happened to find it while
reviewing the code.
> At the very least, we may rename it to "unused_float_high",
> or something, to indicate it is a known-unused?
I don't think renaming solves any problem. Either we keep this variable
as it is or remove it.
>
> Thanks,
>
> /mjt
>
next prev parent reply other threads:[~2016-02-02 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 17:20 [Qemu-trivial] [PATCH 1/2] ARM: PL061: Clear PL061 device state after reset Wei Huang
2016-02-01 17:20 ` [Qemu-devel] " Wei Huang
2016-02-01 17:20 ` [Qemu-trivial] [PATCH 2/2] ARM: PL061: Misc cleaning fields for PL061 device state Wei Huang
2016-02-01 17:20 ` [Qemu-devel] " Wei Huang
2016-02-01 18:01 ` [Qemu-trivial] " Peter Maydell
2016-02-01 18:01 ` [Qemu-devel] " Peter Maydell
2016-02-02 7:03 ` [Qemu-trivial] " Michael Tokarev
2016-02-02 7:03 ` [Qemu-devel] " Michael Tokarev
2016-02-02 15:16 ` Wei Huang [this message]
2016-02-02 15:16 ` Wei Huang
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=56B0C845.9080602@redhat.com \
--to=wei@redhat.com \
--cc=imammedo@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=shannon.zhao@linaro.org \
--cc=zhaoshenglong@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.