From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH 0/4] cuda/mos6522 migration fixes
Date: Thu, 7 Jun 2018 16:18:41 -0300 [thread overview]
Message-ID: <8484d1a4-b9e4-3d69-090c-22c230878566@amsat.org> (raw)
In-Reply-To: <20180607171751.11510-1-mark.cave-ayland@ilande.co.uk>
On 06/07/2018 02:17 PM, Mark Cave-Ayland wrote:
> Whilst performing a random migration test for the Mac machines I noticed
> a regression (patch 1) which prevented the loadvm from completing
> successfully. A big thank you to Peter and David on IRC who pointed me
> in the right direction in order to fix the bug.
>
> Once that was working I spent a bit more time analysing the migration
> stream and realised that the mos6522 device state wasn't being embedded
> within the CUDA device, but instead being maintained separately which is
> solved by patch 2.
>
> Patch 3 is something I noticed whilst rearranging the existing code based
> upon my better understanding of QOM/qdev and ensures that the timer frequency
> is always set correctly post-migration for the device and its parent class.
> This leaves no remaining functionality in the mos6522 realize function and so
> allows it to be removed.
>
> Finally patch 4 was suggested by Peter on IRC whilst helping me investigate
> the original migration issue, and removes the last remaining user of
> VMSTATE_TIMER_PTR_TEST from the codebase.
You forgot patch 5 "vmstate: Remove VMSTATE_TIMER_PTR_TEST" :)
>
> Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
>
>
> Mark Cave-Ayland (4):
> mos6522: fix vmstate_mos6522_timer version in vmstate_mos6522
> cuda: embed mos6522_cuda device directly rather than using QOM object
> link
> mos6522: move timer frequency initialisation to mos6522_reset
> mos6522: convert VMSTATE_TIMER_PTR_TEST to VMSTATE_TIMER_PTR
>
> hw/misc/macio/cuda.c | 50 +++++++++++++++++++-------------------------
> hw/misc/mos6522.c | 26 ++++++-----------------
> include/hw/misc/macio/cuda.h | 27 +++++++++++-------------
> include/hw/misc/mos6522.h | 4 +++-
> 4 files changed, 42 insertions(+), 65 deletions(-)
>
next prev parent reply other threads:[~2018-06-07 19:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 17:17 [Qemu-devel] [PATCH 0/4] cuda/mos6522 migration fixes Mark Cave-Ayland
2018-06-07 17:17 ` [Qemu-devel] [PATCH 1/4] mos6522: fix vmstate_mos6522_timer version in vmstate_mos6522 Mark Cave-Ayland
2018-06-07 17:17 ` [Qemu-devel] [PATCH 2/4] cuda: embed mos6522_cuda device directly rather than using QOM object link Mark Cave-Ayland
2018-06-08 2:13 ` David Gibson
2018-06-07 17:17 ` [Qemu-devel] [PATCH 3/4] mos6522: move timer frequency initialisation to mos6522_reset Mark Cave-Ayland
2018-06-07 17:17 ` [Qemu-devel] [PATCH 4/4] mos6522: convert VMSTATE_TIMER_PTR_TEST to VMSTATE_TIMER_PTR Mark Cave-Ayland
2018-06-07 19:28 ` Peter Maydell
2018-06-07 19:18 ` Philippe Mathieu-Daudé [this message]
2018-06-07 20:17 ` [Qemu-devel] [PATCH 0/4] cuda/mos6522 migration fixes Peter Maydell
2018-06-07 21:10 ` Philippe Mathieu-Daudé
2018-06-08 2:11 ` David Gibson
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=8484d1a4-b9e4-3d69-090c-22c230878566@amsat.org \
--to=f4bug@amsat.org \
--cc=david@gibson.dropbear.id.au \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).