From: Paul Goyette <1693667@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1693667] [NEW] -cpu haswell / broadwell have no MONITOR in features1
Date: Fri, 26 May 2017 03:15:14 -0000 [thread overview]
Message-ID: <149576851455.3442.6872660890935328507.malonedeb@gac.canonical.com> (raw)
Public bug reported:
In qemu 2.9.0 if you run
qemu-system-x86_64 -cpu Broadwell (or Haswell)
then the CPU features1 flag include the SSE3 bit, but do NOT include the
MONITOR/MWAIT bit. This is so even when the host includes the features.
Additionally, running qemu in this manner results in several error messages:
warning: TCG doesn't support requested feature: CPUID.01H:ECX.fma [bit 12]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.avx [bit 28]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.f16c [bit 29]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.rdrand [bit 30]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.avx2 [bit 5]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.rdseed [bit 18]
warning: TCG doesn't support requested feature: CPUID.80000001H:ECX.3dnowprefetch
(Among possible other uses, the lack of the MONITOR feature bit causes NetBSD to fall-back on a
check-and-pause loop while an application CPU is waiting to be told to proceed by the boot CPU.)
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1693667
Title:
-cpu haswell / broadwell have no MONITOR in features1
Status in QEMU:
New
Bug description:
In qemu 2.9.0 if you run
qemu-system-x86_64 -cpu Broadwell (or Haswell)
then the CPU features1 flag include the SSE3 bit, but do NOT include
the MONITOR/MWAIT bit. This is so even when the host includes the
features.
Additionally, running qemu in this manner results in several error messages:
warning: TCG doesn't support requested feature: CPUID.01H:ECX.fma [bit 12]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.tsc-deadline [bit 24]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.avx [bit 28]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.f16c [bit 29]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.rdrand [bit 30]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.hle [bit 4]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.avx2 [bit 5]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.invpcid [bit 10]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.rtm [bit 11]
warning: TCG doesn't support requested feature: CPUID.07H:EBX.rdseed [bit 18]
warning: TCG doesn't support requested feature: CPUID.80000001H:ECX.3dnowprefetch
(Among possible other uses, the lack of the MONITOR feature bit causes NetBSD to fall-back on a
check-and-pause loop while an application CPU is waiting to be told to proceed by the boot CPU.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1693667/+subscriptions
next reply other threads:[~2017-05-26 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 3:15 Paul Goyette [this message]
2020-05-22 5:17 ` [Bug 1693667] Re: -cpu haswell / broadwell have no MONITOR in features1 Thomas Huth
2020-05-22 13:15 ` Paul Goyette
2020-07-22 4:17 ` Launchpad Bug Tracker
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=149576851455.3442.6872660890935328507.malonedeb@gac.canonical.com \
--to=1693667@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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).