From: Paolo Bonzini <pbonzini@redhat.com>
To: Wainer dos Santos Moschetta <wainersm@redhat.com>, qemu-devel@nongnu.org
Cc: ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH] target/i386: Disable MPX support on named CPU models
Date: Thu, 20 Dec 2018 15:25:02 +0100 [thread overview]
Message-ID: <9685dcbe-7236-c03d-47e9-9b1eb30d9a3c@redhat.com> (raw)
In-Reply-To: <490cbc41-0076-659a-9745-29881b9c95cc@redhat.com>
On 20/12/18 15:18, Wainer dos Santos Moschetta wrote:
>
> On 12/20/2018 10:11 AM, Paolo Bonzini wrote:
>> MPX support is being phased out by Intel; GCC has dropped it, Linux
>> is also going to do that. Even though KVM will have special code
>> to support MPX after the kernel proper stops enabling it in XCR0,
>> we probably also want to deprecate that in a few years. As a start,
>> do not enable it by default for any named CPU model starting with
>> the 4.0 machine types; this include Skylake, Icelake and Cascadelake.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> include/hw/i386/pc.h | 29 +++++++++++++++++++++++++++++
>> target/i386/cpu.c | 14 +++++++-------
>> 2 files changed, 36 insertions(+), 7 deletions(-)
>
> Side question: I didn't find on QEMU's user manual any reference to
> deprecated features for CPU models. Does that information exists
> somewhere? If not, should it be documented for the users?
It's not deprecated yet, as it won't be removed until pc-*-3.1 is
deprecated. It may be deprecated together with pc-*-3.1, or maybe not
since TCG does implement MPX.
Paolo
prev parent reply other threads:[~2018-12-20 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 12:11 [Qemu-devel] [PATCH] target/i386: Disable MPX support on named CPU models Paolo Bonzini
2018-12-20 14:18 ` Wainer dos Santos Moschetta
2018-12-20 14:25 ` 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=9685dcbe-7236-c03d-47e9-9b1eb30d9a3c@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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 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).