From: Paul Lai <paul.c.lai@intel.com>
To: qemu-devel@nongnu.org
Cc: wei.w.wang@intel.com, luwei.kang@intel.com, tao3.xu@intel.com,
paul.c.lai@intel.com
Subject: [Qemu-devel] Add SPLIT_LOCK DETECT capability to SnowRidge (SNR) cpu model
Date: Wed, 26 Jun 2019 09:32:32 -0700 [thread overview]
Message-ID: <20190626163232.25711-1-paul.c.lai@intel.com> (raw)
SPLIT_LOCK DETECT is enabled in qemu patch:
x86: define a new MSR based feature word -- FEAT_CORE_CAPABILITY
and kernel patch series that includes:
x86/split_lock: Align x86_capability to unsigned long to avoid split locked
access
WAITPKG (UMONITOR/UMWAIT/TPAUSE) supplied in:
x86/cpu: Add support for UMONITOR/UMWAIT/TPAUSE
are turned off by default, so not added to this cpu model.
Signed-off-by: Paul Lai <paul.c.lai@intel.com>
Tested-by: Tao3 Xu <tao3.xu@intel.com>
---
Changes in v4:
Add SPLIT_LOCK DETECT capability to SnowRidge (SNR) cpu model
---
target/i386/cpu.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index c96f032f03..63d89276fe 100644
--- a/target/i386/cpu.c
+++ b/target/i386/cpu.c
@@ -2739,7 +2739,10 @@ static X86CPUDefinition builtin_x86_defs[] = {
CPUID_7_0_ECX_MOVDIR64B,
.features[FEAT_7_0_EDX] =
CPUID_7_0_EDX_SPEC_CTRL |
- CPUID_7_0_EDX_ARCH_CAPABILITIES | CPUID_7_0_EDX_SPEC_CTRL_SSBD,
+ CPUID_7_0_EDX_ARCH_CAPABILITIES | CPUID_7_0_EDX_SPEC_CTRL_SSBD |
+ CPUID_7_0_EDX_CORE_CAPABILITY,
+ .features[FEAT_CORE_CAPABILITY] =
+ MSR_CORE_CAP_SPLIT_LOCK_DETECT,
/*
* Missing: XSAVES (not supported by some Linux versions,
* including v4.1 to v4.12).
--
2.17.2
reply other threads:[~2019-06-26 16:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190626163232.25711-1-paul.c.lai@intel.com \
--to=paul.c.lai@intel.com \
--cc=luwei.kang@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=tao3.xu@intel.com \
--cc=wei.w.wang@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).