From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Marc Mar? <markmb@redhat.com>,
qemu-devel@nongnu.org, Alexandre DERUMIER <aderumier@odiso.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fw_cfg: unbreak migration compatibility for 2.4 and earlier machines
Date: Fri, 19 Feb 2016 08:09:54 +0100 [thread overview]
Message-ID: <1455865794.29896.3.camel@redhat.com> (raw)
In-Reply-To: <1455823860-22268-1-git-send-email-lersek@redhat.com>
On Do, 2016-02-18 at 20:31 +0100, Laszlo Ersek wrote:
> When I reviewed Marc's fw_cfg DMA patches, I completely missed that the
> way we set dma_enabled would break migration.
Patch looks fine to me ...
> Not tested:
> * actual migration
> * when board code doesn't request DMA support
>
> Testing feedback from people who use migration would be nice.
... but some actual migration testing would be great indeed.
thanks,
Gerd
next prev parent reply other threads:[~2016-02-19 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 19:31 [Qemu-devel] [PATCH] fw_cfg: unbreak migration compatibility for 2.4 and earlier machines Laszlo Ersek
2016-02-19 7:09 ` Gerd Hoffmann [this message]
2016-02-19 8:06 ` Alexandre DERUMIER
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=1455865794.29896.3.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=aderumier@odiso.com \
--cc=lersek@redhat.com \
--cc=markmb@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.