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: Thu, 19 Nov 2015 13:02:40 +0100 [thread overview]
Message-ID: <564DBA60.2010707@redhat.com> (raw)
In-Reply-To: <CANRm+CwK1C8ZhCvYWZdShgPLXGj+FPuAsvDcVxB_WOXVdwoxKQ@mail.gmail.com>
On 19/11/2015 13:01, Wanpeng Li wrote:
> > This is not correct. As far as I know, the SYSCALL bit is always
> > present in CPUID, even if the machine is running in 32-bit mode; CPUID
> > documentation (SDM Volume 2) explicitly documents bit 11 as "Bit 11:
> > SYSCALL/SYSRET available in 64-bit mode".
>
> No, I try a 32-bit linux host kernel, cpuid tool shows that SYSCALL
> bit is not set.
Ok, let me try...
Paolo
next prev parent reply other threads:[~2015-11-19 12:02 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 [this message]
2015-11-25 12:45 ` Wanpeng Li
2015-11-25 13:27 ` Paolo Bonzini
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=564DBA60.2010707@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