From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Marcelo Tosatti <mtosatti@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Igor Mammedov <imammedo@redhat.com>
Subject: [Qemu-devel] [qom-cpu PATCH v2 0/2] target-i386: Fixes for migratable/invtsc
Date: Fri, 16 May 2014 14:58:46 -0300 [thread overview]
Message-ID: <1400263128-19107-1-git-send-email-ehabkost@redhat.com> (raw)
This series contains two fixes for the qom-cpu branch:
* Make the new "migratable" property actually work;
* Avoid breaking setups where "-cpu host" needs to be migratable.
(See discussion at http://marc.info/?l=qemu-devel&m=139838802220184&w=2 )
Cc: Andreas Färber <afaerber@suse.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>
Cc: Aurelien Jarno <aurelien@aurel32.net>
Cc: Richard Henderson <rth@twiddle.net>
Eduardo Habkost (2):
target-i386: Use x86_cpu_get_supported_feature_word() for "-cpu host"
target-i386: Set migratable=yes by default on "host" CPU mooel
target-i386/cpu.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
--
1.9.0
next reply other threads:[~2014-05-16 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 17:58 Eduardo Habkost [this message]
2014-05-16 17:58 ` [Qemu-devel] [qom-cpu PATCH v2 1/2] target-i386: Use x86_cpu_get_supported_feature_word() for "-cpu host" Eduardo Habkost
2014-05-16 17:58 ` [Qemu-devel] [qom-cpu PATCH v2 2/2] target-i386: Set migratable=yes by default on "host" CPU mooel Eduardo Habkost
2014-06-02 20:45 ` [Qemu-devel] [qom-cpu PATCH v2 0/2] target-i386: Fixes for migratable/invtsc Eduardo Habkost
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=1400263128-19107-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=aurelien@aurel32.net \
--cc=imammedo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).