From: Tao Xu <tao3.xu@intel.com>
To: ehabkost@redhat.com
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Guo, Xuelian" <xuelian.guo@intel.com>
Subject: About MONITOR/MWAIT in i386 CPU model
Date: Wed, 13 Nov 2019 16:42:25 +0800 [thread overview]
Message-ID: <d52ddfd1-3d9d-6a3a-5ce9-893df96639cc@intel.com> (raw)
Hi Eduardo,
After kvm use "-overcommit cpu-pm=on" to expose MONITOR/MWAIT
(commit id 6f131f13e68d648a8e4f083c667ab1acd88ce4cd), the MONITOR/MWAIT
feature in CPU model (phenom core2duo coreduo n270 Opteron_G3 EPYC
Snowridge Denverton) may be unused. For example, when we boot a guest
with Denverton cpu model, guest cannot detect MONITOR and boot with no
warning. Should we remove this feature from some CPU model?
Tested by Guo, Xuelian <xuelian.guo@intel.com>
Tao Xu
next reply other threads:[~2019-11-13 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 8:42 Tao Xu [this message]
2019-11-13 22:47 ` About MONITOR/MWAIT in i386 CPU model Eduardo Habkost
2019-11-14 0:50 ` Tao Xu
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=d52ddfd1-3d9d-6a3a-5ce9-893df96639cc@intel.com \
--to=tao3.xu@intel.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xuelian.guo@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).