From: Laurent Vivier <laurent@vivier.eu>
To: "Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [PATCH] hw/timer/etraxfs_timer: Add vmstate for ETRAX timers
Date: Wed, 12 Jan 2022 15:29:54 +0100 [thread overview]
Message-ID: <e101fbe8-c69c-7735-3fd0-acee907754fe@vivier.eu> (raw)
In-Reply-To: <5cad7d04-1699-35d2-8d96-b236d451101d@linaro.org>
Le 18/12/2021 à 03:28, Richard Henderson a écrit :
> On 12/17/21 3:37 PM, Philippe Mathieu-Daudé wrote:
>> ping?
>>
>> On 11/6/21 11:56, Philippe Mathieu-Daudé wrote:
>>> Add the vmstate for the ETRAX timers.
>>> This is in theory a migration compatibility break
>>> for the 'AXIS devboard 88' CRIS machine.
>>>
>>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>>> ---
>>> hw/timer/etraxfs_timer.c | 34 +++++++++++++++++++++++++++++++++-
>>> 1 file changed, 33 insertions(+), 1 deletion(-)
>
>
> In that it matches another similar timer device:
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>
>
>>> +static const VMStateDescription vmstate_etraxfs = {
>>> + .name = "etraxfs",
>>> + .version_id = 0,
>>> + .minimum_version_id = 0,
>>> + .fields = (VMStateField[]) {
>>> + VMSTATE_PTIMER(ptimer_t0, ETRAXTimerState),
>>> + VMSTATE_PTIMER(ptimer_t1, ETRAXTimerState),
>>> + VMSTATE_PTIMER(ptimer_wd, ETRAXTimerState),
>>> +
>>> + VMSTATE_UINT32(wd_hits, ETRAXTimerState),
>>> +
>>> + VMSTATE_UINT32(rw_tmr0_div, ETRAXTimerState),
>>> + VMSTATE_UINT32(r_tmr0_data, ETRAXTimerState),
>>> + VMSTATE_UINT32(rw_tmr0_ctrl, ETRAXTimerState),
>>> +
>>> + VMSTATE_UINT32(rw_tmr1_div, ETRAXTimerState),
>>> + VMSTATE_UINT32(r_tmr1_data, ETRAXTimerState),
>>> + VMSTATE_UINT32(rw_tmr1_ctrl, ETRAXTimerState),
>>> +
>>> + VMSTATE_UINT32(rw_wd_ctrl, ETRAXTimerState),
>>> +
>>> + VMSTATE_UINT32(rw_intr_mask, ETRAXTimerState),
>>> + VMSTATE_UINT32(rw_ack_intr, ETRAXTimerState),
>>> + VMSTATE_UINT32(r_intr, ETRAXTimerState),
>>> + VMSTATE_UINT32(r_masked_intr, ETRAXTimerState),
>>> +
>>> + VMSTATE_END_OF_LIST()
>>> + }
>>> +};
>
> What I don't understand is how these controls get applied to qemu_irq after vmload, here or in any
> other device. It seems like we should have some post_load hook that calls timer_update_irq, etc.
>
FWIW, in VMSTATE_PTIMER(), we use a vmstate_ptimer struct that registers a vmstate_info_timer with
VMSTATE_TIMER_PTR(). vmstate_info_timer uses timer_get() to update or delete the timer when it is
loaded.
Applied to my trivial-patches branch.
Thanks,
Laurent
next prev parent reply other threads:[~2022-01-12 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 10:56 [PATCH] hw/timer/etraxfs_timer: Add vmstate for ETRAX timers Philippe Mathieu-Daudé
2021-12-17 23:37 ` Philippe Mathieu-Daudé
2021-12-18 2:28 ` Richard Henderson
2022-01-12 14:29 ` Laurent Vivier [this message]
2022-01-12 16:02 ` 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=e101fbe8-c69c-7735-3fd0-acee907754fe@vivier.eu \
--to=laurent@vivier.eu \
--cc=edgar.iglesias@gmail.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.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).