From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Cc: Xiaoyao Li <xiaoyao.li@intel.com>, qemu-devel@nongnu.org
Subject: [PATCH 0/2] Fixes for env->user_features
Date: Tue, 14 Jul 2020 01:44:34 +0800 [thread overview]
Message-ID: <20200713174436.41070-1-xiaoyao.li@intel.com> (raw)
Patch 1 fixes the env->features set by versioned CPU model.
Patch 2 fixed the env->features set by unavailable_features due to
feature_dependencies[] checking.
Xiaoyao Li (2):
i368/cpu: Clear env->user_features after loading versioned CPU model
i386/cpu: Don't add unavailable_features to env->user_features
target/i386/cpu.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
--
2.18.4
next reply other threads:[~2020-07-13 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 17:44 Xiaoyao Li [this message]
2020-07-13 17:44 ` [PATCH 1/2] i368/cpu: Clear env->user_features after loading versioned CPU model Xiaoyao Li
2020-07-13 18:44 ` Eduardo Habkost
2020-07-13 17:44 ` [PATCH 2/2] i386/cpu: Don't add unavailable_features to env->user_features Xiaoyao Li
2020-07-13 18:48 ` Eduardo Habkost
2020-07-27 12:01 ` Paolo Bonzini
2020-07-13 18:08 ` [PATCH 0/2] Fixes for env->user_features no-reply
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=20200713174436.41070-1-xiaoyao.li@intel.com \
--to=xiaoyao.li@intel.com \
--cc=ehabkost@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).