From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Uri Lublin <uril@redhat.com>
Subject: Re: [Qemu-devel] [RESEND][QUERY] savevm/loadvm/migration of usb devices - do we save enough information.
Date: Thu, 15 Jan 2009 14:35:52 -0600 [thread overview]
Message-ID: <496F9E28.1010904@codemonkey.ws> (raw)
In-Reply-To: <496DFFAF.3040006@redhat.com>
Uri Lublin wrote:
> Hello,
>
> Currently Qemu does not save/load state information for all usb
> devices, but
> only save/load state information for usb-uhci (r5054).
>
> Is it enough ? Doesn't Qemu need to save e.g.
> speed/addr/state/setup_state for
> USBDevice's ?
I presume so.
Regards,
Anthony Liguori
> As a reference look at the patch at the bottom of [1], specifically at
> generic_usb_save/generic_usb_load.
>
> Thanks,
> Uri.
>
> [1]
> http://www.mail-archive.com/kvm-devel@lists.sourceforge.net/msg05898.html
>
>
>
>
prev parent reply other threads:[~2009-01-15 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 15:07 [Qemu-devel] [RESEND][QUERY] savevm/loadvm/migration of usb devices - do we save enough information Uri Lublin
2009-01-15 20:35 ` Anthony Liguori [this message]
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=496F9E28.1010904@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=uril@redhat.com \
/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).