[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v2 0/2] g364fb: fix migration (or: fix migration for MIPS magnum
From: |
Mark Cave-Ayland |
Subject: |
[PATCH v2 0/2] g364fb: fix migration (or: fix migration for MIPS magnum machines) |
Date: |
Fri, 25 Jun 2021 17:35:52 +0100 |
I noticed whilst testing the previous dp8393x patchset that I would always
get a segfault whilst attempting to migrate the MIPS magnum machine.
A bit of detective work shows that the problem is an incorrect
VMStateDescription
in the g364fb device which expects a G364State but instead receives a
G364SysBusState.
Looking back through the git history suggests that migration for this device
(and also the MIPS magnum machines) has been broken for several years, so patch
1 takes the opportunity to improve the migration stream for the framebuffer
first whilst patch 2 contains the actual fix.
Note that I don't use the MIPS magnum machines on a regular basis but the
patchset fixes the migration error and survives some light testing here.
Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
v2:
- Bump migration version to 2 as suggested by Phil (note: I've done this in
both patch 1 and patch 2 to keep the versions identical)
- Remove unused vram pointer from G364State in patch 1
- Added R-B tag from Phil
Mark Cave-Ayland (2):
g364fb: use RAM memory region for framebuffer
g364fb: add VMStateDescription for G364SysBusState
hw/display/g364fb.c | 32 ++++++++++++++++++++------------
1 file changed, 20 insertions(+), 12 deletions(-)
--
2.20.1
- [PATCH v2 0/2] g364fb: fix migration (or: fix migration for MIPS magnum machines),
Mark Cave-Ayland <=