From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
Mike Day <ncmike@ncultra.org>, Gerd Hoffmann <kraxel@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] usb-ohci: add vmstate descriptor
Date: Sat, 22 Mar 2014 22:04:40 +0100 [thread overview]
Message-ID: <532DFAE8.90704@suse.de> (raw)
In-Reply-To: <CAFEAcA_oE0H6mkLmBpVri5B7OorEcqyOd+GpV+XfQSDnEsUjPw@mail.gmail.com>
Am 22.03.2014 21:54, schrieb Peter Maydell:
> On 22 March 2014 20:18, Andreas Färber <afaerber@suse.de> wrote:
>> Because AFAIU
>> migration is possible without VMSD, just not with VMSD that sets
>> .unmigratable = 1.
>
> Well, the migration won't fail with an error, but on the destination
> end you'll end up with a device in its reset state but a guest which
> may think the device is in some other state. If the device was
> quiescent and doesn't need complex setup it might cope, but
> more likely is that that guest driver will fall over in a heap next
> time you try to use it...
Well, there is no OHCI state being added, only PCI state. So I'd be
curious to know what in there is the problem because a general review of
PCI devices might be due then - and ideally before we do the release.
Cheers,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-03-22 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 6:43 [Qemu-devel] [PATCH] usb-ohci: add vmstate descriptor Alexey Kardashevskiy
2014-03-06 13:57 ` Mike Day
2014-03-14 5:09 ` Alexey Kardashevskiy
2014-03-22 20:18 ` Andreas Färber
2014-03-22 20:54 ` Peter Maydell
2014-03-22 21:04 ` Andreas Färber [this message]
2014-03-22 21:23 ` Peter Maydell
2014-03-24 5:53 ` Alexey Kardashevskiy
2014-03-24 9:26 ` Peter Maydell
2014-03-24 10:26 ` Gerd Hoffmann
2014-03-22 21:50 ` Alexey Kardashevskiy
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=532DFAE8.90704@suse.de \
--to=afaerber@suse.de \
--cc=aik@ozlabs.ru \
--cc=kraxel@gmail.com \
--cc=ncmike@ncultra.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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.