From: Vincent Bernat <vincent@bernat.im>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-i386: add pcid to both Sandy Bridge and Ivy Bridge
Date: Tue, 09 Jan 2018 08:04:26 +0100 [thread overview]
Message-ID: <m3mv1n8qdh.fsf@luffy.cx> (raw)
In-Reply-To: <20180108231917.GQ6646@localhost.localdomain> (Eduardo Habkost's message of "Mon, 8 Jan 2018 21:19:17 -0200")
❦ 8 janvier 2018 21:19 -0200, Eduardo Habkost <ehabkost@redhat.com> :
>> > GET_SUPPORTED_CPUID seems to still return PCID as supported
>> > without EPT, doesn't it?
>>
>> Indeed it is! It will also be useful for KPTI performance without
>> INVPCID, but it won't be useful without EPT.
>
> Well, I can live with "not useful without EPT", as long as it
> doesn't mean "broken without EPT". It looks like we can safely
> enable it, as long as:
>
> 2) we confirm if all Intel Westmere/SandyBridge/IvyBridge CPUs
> have PCID;
I didn't find an authoritative information about that on Intel
website. Various sites indeed says the feature was introduced in
Westmere. And Greg KH mentions Westmere here too:
https://mail-archive.com/linux-kernel@vger.kernel.org/msg1576774.html
> 1) QEMU documentation states that it requires Linux v3.6 or newer
> for KVM.
I have updated the patch and sent it in a new thread. It's now based on
x86-next.
--
Clothes make the man. Naked people have little or no influence on society.
-- Mark Twain
next prev parent reply other threads:[~2018-01-09 7:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 20:50 [Qemu-devel] [PATCH] target-i386: add pcid to both Sandy Bridge and Ivy Bridge Vincent Bernat
2018-01-08 21:16 ` Eduardo Habkost
2018-01-08 21:51 ` Vincent Bernat
2018-01-08 22:14 ` Eduardo Habkost
2018-01-08 22:22 ` Vincent Bernat
2018-01-08 22:28 ` Eduardo Habkost
2018-01-08 22:37 ` Paolo Bonzini
2018-01-08 22:56 ` Eduardo Habkost
2018-01-08 23:09 ` Paolo Bonzini
2018-01-08 23:19 ` Eduardo Habkost
2018-01-09 7:04 ` Vincent Bernat [this message]
2018-01-09 6:41 ` Vincent Bernat
2018-01-09 6:40 ` Vincent Bernat
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=m3mv1n8qdh.fsf@luffy.cx \
--to=vincent@bernat.im \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.