From: "H. Peter Anvin" <hpa@zytor.com>
To: Jet Chen <jet.chen@intel.com>,
"Romer, Benjamin M" <Benjamin.Romer@unisys.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Borislav Petkov <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP
Date: Fri, 11 Apr 2014 10:40:43 -0700 [thread overview]
Message-ID: <5348291B.7090501@zytor.com> (raw)
In-Reply-To: <534827F5.1020004@intel.com>
On 04/11/2014 10:35 AM, Jet Chen wrote:
>
> As Peter said, QEMU probably should *not* set the hypervisor bit. But based on my testing, I think KVM works properly in this case.
>
Either way, unless there is a CPUID interface exposed in CPUID levels
0x40000000+, then relying on the hypervisor bit to do VMCALL is wrong in
the extreme.
-hpa
next prev parent reply other threads:[~2014-04-11 17:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 11:17 [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP Fengguang Wu
2014-04-07 14:04 ` Ken Cox
2014-04-07 14:09 ` Greg Kroah-Hartman
2014-04-07 14:24 ` Ken Cox
2014-04-07 19:23 ` Greg Kroah-Hartman
2014-04-07 19:46 ` Greg Kroah-Hartman
[not found] ` <C97001BC43954D438ACB059713BA5CDF92040F0F00@USEA-EXCH7.na.uis.unisys.com>
2014-04-08 2:53 ` Fengguang Wu
2014-04-08 15:39 ` Romer, Benjamin M
[not found] ` <53444220.50009@intel.com>
[not found] ` <C97001BC43954D438ACB059713BA5CDF92040F0F06@USEA-EXCH7.na.uis.unisys.com>
[not found] ` <53458A3A.1050608@intel.com>
2014-04-09 23:01 ` Fengguang Wu
2014-04-09 23:10 ` H. Peter Anvin
2014-04-10 13:19 ` Romer, Benjamin M
2014-04-11 2:28 ` H. Peter Anvin
2014-04-11 13:51 ` Romer, Benjamin M
2014-04-11 16:33 ` H. Peter Anvin
2014-04-11 17:35 ` Jet Chen
2014-04-11 17:40 ` H. Peter Anvin [this message]
2014-04-11 17:51 ` Romer, Benjamin M
2014-04-30 10:02 ` Paolo Bonzini
2014-04-11 17:49 ` Romer, Benjamin M
2014-04-13 11:51 ` Borislav Petkov
2014-04-13 12:20 ` Jet Chen
2014-04-09 23:10 ` H. Peter Anvin
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=5348291B.7090501@zytor.com \
--to=hpa@zytor.com \
--cc=Benjamin.Romer@unisys.com \
--cc=bp@alien8.de \
--cc=fengguang.wu@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.