From: Andre Przywara <andre.przywara@amd.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] CPUID feature bits not saved with migration
Date: Wed, 15 Jul 2009 14:50:56 +0200 [thread overview]
Message-ID: <4A5DD0B0.7070700@amd.com> (raw)
Hi,
while testing the guest multi-core code, I realized that all of the
cpuid_* values (like cpuid_ext_features,...) from CPUX86State are not
dumped in the migration stream. Is this intentional behavior (to let the
user specify other bits in the target?) or has this just been forgotten?
Does KVM call the SET_CPUID2 ioctl after or before migration?
Regards,
Andre.
--
Andre Przywara
AMD-OSRC (Dresden)
Tel: x29712
next reply other threads:[~2009-07-15 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 12:50 Andre Przywara [this message]
2009-07-15 14:38 ` [Qemu-devel] CPUID feature bits not saved with migration Anthony Liguori
2009-07-15 15:12 ` Jamie Lokier
2009-07-16 6:55 ` Dor Laor
2009-07-16 10:09 ` Andre Przywara
2009-07-16 14:29 ` Jamie Lokier
2009-07-16 10:08 ` Andre Przywara
2009-07-16 14:28 ` Jamie Lokier
2009-07-22 13:24 ` Andre Przywara
2009-07-22 14:46 ` Jamie Lokier
2009-07-16 10:08 ` Andre Przywara
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=4A5DD0B0.7070700@amd.com \
--to=andre.przywara@amd.com \
--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 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).