From: Chenyi Qiang <chenyi.qiang@intel.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>
Cc: Xiaoyao Li <xiaoyao.li@intel.com>,
Chenyi Qiang <chenyi.qiang@intel.com>,
qemu-devel@nongnu.org
Subject: [PATCH v2 2/2] target/i386: Remove core-capability in Snowridge CPU model
Date: Fri, 27 Aug 2021 14:48:18 +0800 [thread overview]
Message-ID: <20210827064818.4698-3-chenyi.qiang@intel.com> (raw)
In-Reply-To: <20210827064818.4698-1-chenyi.qiang@intel.com>
Because core-capability releated features are model-specific and KVM
won't support it, remove the core-capability in CPU model to avoid the
warning message.
Signed-off-by: Chenyi Qiang <chenyi.qiang@intel.com>
---
target/i386/cpu.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index aebf81d9c9..86a15af1ed 100644
--- a/target/i386/cpu.c
+++ b/target/i386/cpu.c
@@ -3684,9 +3684,10 @@ static const X86CPUDefinition builtin_x86_defs[] = {
},
{
.version = 4,
- .note = "no split lock detect",
+ .note = "no split lock detect, no core-capability",
.props = (PropValue[]) {
{ "split-lock-detect", "off" },
+ { "core-capability", "off" },
{ /* end of list */ },
},
},
--
2.17.1
next prev parent reply other threads:[~2021-08-27 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 6:48 [PATCH v2 0/2] Remove unsupported features in SNR CPU model Chenyi Qiang
2021-08-27 6:48 ` [PATCH v2 1/2] target/i386: Remove split lock detect in Snowridge " Chenyi Qiang
2021-08-27 6:48 ` Chenyi Qiang [this message]
2021-10-11 8:31 ` [PATCH v2 2/2] target/i386: Remove core-capability " Chenyi Qiang
2021-10-15 15:07 ` [PATCH v2 0/2] Remove unsupported features in SNR " 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=20210827064818.4698-3-chenyi.qiang@intel.com \
--to=chenyi.qiang@intel.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=xiaoyao.li@intel.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).