From: "H. Peter Anvin" <hpa@zytor.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Ren, Qiaowei" <qiaowei.ren@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Xudong Hao <xudong.hao@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Qemu-devel] [PATCH v2 3/3] X86, mpx: Intel MPX xstate feature definition
Date: Fri, 06 Dec 2013 13:33:50 -0800 [thread overview]
Message-ID: <52A242BE.3010701@zytor.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC82923350140B3B6@SHSMSX101.ccr.corp.intel.com>
On 12/06/2013 12:05 PM, Liu, Jinsong wrote:
>>
>> Since Peter already said the same, please undo these changes.
>>
>> Also, how is XSTATE_EAGER used? Should MPX be disabled when xsaveopt
>> is disabled on the kernel command line? (Liu, how would this affect
>> the KVM patches, too?)
>>
>> Paolo
>
> Currently seems no, and if needed we can add a new patch at kvm side accordingly when native mpx patches checked in.
>
We need to either disable these features in lazy mode, or we need to
force eager mode if these features are to be supported. The problem
with the latter is that it means forcing eager mode regardless of if
anything actually *uses* these features.
A third option would be to require applications to use a prctl() or
similar to enable eager-save features.
Thoughts?
-hpa
next prev parent reply other threads:[~2013-12-06 21:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 0:20 [PATCH v2 1/3] x86, mpx: add documentation on Intel MPX Qiaowei Ren
2013-12-07 0:20 ` [PATCH v2 2/3] X86, mpx: Intel MPX CPU feature definition Qiaowei Ren
2013-12-07 0:20 ` [PATCH v2 3/3] X86, mpx: Intel MPX xstate " Qiaowei Ren
2013-12-06 17:35 ` Paolo Bonzini
2013-12-06 17:55 ` H. Peter Anvin
2013-12-06 20:05 ` Liu, Jinsong
2013-12-06 21:33 ` H. Peter Anvin [this message]
2013-12-06 22:12 ` Liu, Jinsong
2013-12-07 0:23 ` Ren, Qiaowei
2013-12-07 1:07 ` H. Peter Anvin
2013-12-07 1:16 ` [Qemu-devel] " Ren, Qiaowei
2013-12-07 1:19 ` 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=52A242BE.3010701@zytor.com \
--to=hpa@zytor.com \
--cc=jinsong.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qiaowei.ren@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xudong.hao@intel.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