From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: Wanpeng li <wanpeng.li@hotmail.com>, kvm <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: x86: don't expose syscall/sysret to intel 32-bit guest
Date: Wed, 25 Nov 2015 14:27:40 +0100 [thread overview]
Message-ID: <5655B74C.6070305@redhat.com> (raw)
In-Reply-To: <CANRm+CxoipUJEzx0MBMbG84GLmf_f+3fSs1YOPTwme2dwZ7UDA@mail.gmail.com>
On 25/11/2015 13:45, Wanpeng Li wrote:
> 2015-11-19 19:05 GMT+08:00 Paolo Bonzini <pbonzini@redhat.com>:
>>
>> 1) Clear F(SYSCALL) in kvm_update_cpuid, like you are doing here but
>> only if F(LM) is already clear (in addition to the vendor being Intel).
>
> It seems that F(LM) is always set in the case of qemu-system-x86_64 w/
> 32-bit guest, vmware also exposes LM bit to 32 bit guest(however it
> doesn't expose syscall/sysret)
Does it expose the SYSCALL bit?
Paolo
prev parent reply other threads:[~2015-11-25 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BLU436-SMTP15906F5C0F0430EFB140F45801B0@phx.gbl>
2015-11-19 11:05 ` [PATCH] KVM: x86: don't expose syscall/sysret to intel 32-bit guest Paolo Bonzini
2015-11-19 12:01 ` Wanpeng Li
2015-11-19 12:02 ` Paolo Bonzini
2015-11-25 12:45 ` Wanpeng Li
2015-11-25 13:27 ` Paolo Bonzini [this message]
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=5655B74C.6070305@redhat.com \
--to=pbonzini@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wanpeng.li@hotmail.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