From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, agraf@suse.de,
jsnow@redhat.com
Subject: [Qemu-devel] [PATCH 2/4] macio: add dma_active to VMStateDescription
Date: Wed, 6 Jan 2016 20:37:24 +0000 [thread overview]
Message-ID: <1452112646-15969-3-git-send-email-mark.cave-ayland@ilande.co.uk> (raw)
In-Reply-To: <1452112646-15969-1-git-send-email-mark.cave-ayland@ilande.co.uk>
Make sure that we include the value of dma_active in the migration stream.
Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
---
hw/ide/macio.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/ide/macio.c b/hw/ide/macio.c
index 560c071..695d4d2 100644
--- a/hw/ide/macio.c
+++ b/hw/ide/macio.c
@@ -518,11 +518,12 @@ static const MemoryRegionOps pmac_ide_ops = {
static const VMStateDescription vmstate_pmac = {
.name = "ide",
- .version_id = 3,
+ .version_id = 4,
.minimum_version_id = 0,
.fields = (VMStateField[]) {
VMSTATE_IDE_BUS(bus, MACIOIDEState),
VMSTATE_IDE_DRIVES(bus.ifs, MACIOIDEState),
+ VMSTATE_BOOL(dma_active, MACIOIDEState),
VMSTATE_END_OF_LIST()
}
};
--
1.7.10.4
next prev parent reply other threads:[~2016-01-06 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 20:37 [Qemu-devel] [PATCH 0/4] ppc: loadvm/savevm fixups for macio/DBDMA Mark Cave-Ayland
2016-01-06 20:37 ` [Qemu-devel] [PATCH 1/4] macio: use the existing IDEDMA aiocb to hold the active DMA aiocb Mark Cave-Ayland
2016-01-06 21:09 ` John Snow
2016-01-06 20:37 ` Mark Cave-Ayland [this message]
2016-01-06 20:57 ` [Qemu-devel] [PATCH 2/4] macio: add dma_active to VMStateDescription John Snow
2016-01-06 21:17 ` Mark Cave-Ayland
2016-01-08 20:55 ` John Snow
2016-01-11 23:41 ` Mark Cave-Ayland
2016-01-14 16:51 ` John Snow
2016-01-14 20:18 ` Mark Cave-Ayland
2016-01-06 20:37 ` [Qemu-devel] [PATCH 3/4] mac_dbdma: add DBDMA controller state " Mark Cave-Ayland
2016-01-06 20:37 ` [Qemu-devel] [PATCH 4/4] cuda: add missing fields " Mark Cave-Ayland
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=1452112646-15969-3-git-send-email-mark.cave-ayland@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=agraf@suse.de \
--cc=jsnow@redhat.com \
--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).