From: Eduardo Habkost <ehabkost@redhat.com>
To: Huaitong Han <huaitong.han@intel.com>
Cc: pbonzini@redhat.com, rth@twiddle.net, afaerber@suse.de,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v3 1/3] target-i386: add pkeys support for cpuid handling
Date: Wed, 18 Nov 2015 13:58:55 -0200 [thread overview]
Message-ID: <20151118155855.GI20436@thinpad.lan.raisama.net> (raw)
In-Reply-To: <1447813217-10532-2-git-send-email-huaitong.han@intel.com>
On Wed, Nov 18, 2015 at 10:20:15AM +0800, Huaitong Han wrote:
[...]
> @@ -408,6 +420,13 @@ static FeatureWordInfo feature_word_info[FEATURE_WORDS] = {
> .cpuid_reg = R_EBX,
> .tcg_features = TCG_7_0_EBX_FEATURES,
> },
> + [FEAT_7_0_ECX] = {
> + .feat_names = cpuid_7_0_ecx_feature_name,
> + .cpuid_eax = 7,
> + .cpuid_needs_ecx = true, .cpuid_ecx = 0,
> + .cpuid_reg = R_ECX,
> + .tcg_features = TCG_7_0_ECX_FEATURES,
> + },
The patch looks good, but when we add the feature names to
cpuid_7_0_ecx_feature_name, QEMU will consider them as
migratable, but they are truly migratable only after we add the
ext_save_areas entry.
We can fix this by moving cpuid_7_0_ecx_feature_name to patch 2/3
(or to a separate patch, to be applied after 2/3).
--
Eduardo
next prev parent reply other threads:[~2015-11-18 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 2:20 [PATCH v3 0/3] target-i386: add memory protection-key support Huaitong Han
2015-11-18 2:20 ` [PATCH v3 1/3] target-i386: add pkeys support for cpuid handling Huaitong Han
2015-11-18 15:58 ` Eduardo Habkost [this message]
2015-11-19 6:36 ` [Qemu-devel] " Han, Huaitong
2015-11-19 11:10 ` Paolo Bonzini
2015-11-19 14:56 ` Eduardo Habkost
2015-11-18 2:20 ` [PATCH v3 2/3] target-i386: add pkeys support for xsave state handling Huaitong Han
2015-11-18 2:20 ` [PATCH v3 3/3] target-i386: add pkeys support for vm migration Huaitong Han
2015-11-18 17:51 ` [Qemu-devel] [PATCH v3 0/3] target-i386: add memory protection-key support Eduardo Habkost
2015-11-18 21:28 ` Paolo Bonzini
2015-12-04 14:57 ` 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=20151118155855.GI20436@thinpad.lan.raisama.net \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=huaitong.han@intel.com \
--cc=kvm@vger.kernel.org \
--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