From: Yu-cheng Yu <yu-cheng.yu@intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
Borislav Petkov <bp@suse.de>,
Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH v2 0/9] x86/xsaves: Fix XSAVES known issues
Date: Thu, 25 Feb 2016 13:07:15 -0800 [thread overview]
Message-ID: <20160225210715.GA8948@test-lenovo> (raw)
In-Reply-To: <56CF6AB8.1050803@linux.intel.com>
On Thu, Feb 25, 2016 at 12:57:28PM -0800, Dave Hansen wrote:
> On 02/25/2016 12:26 PM, Yu-cheng Yu wrote:
> > Patch 9 re-enables XSAVES.
>
> Could we also add one more thing to this: A big, fat warning that
> supervisor states are not supported? We might get that from an eventual
> use of xfeature_uncompacted_offset(), but we need something that's very
> clear.
>
> I just don't want somebody coming along and shoving a supervisor state
> in to XCR0 and expecting it to work just because we have XSAVES support
> itself. That might happen in-tree or out-of-tree as things get prototyped.
I will do that.
Yu-cheng
prev parent reply other threads:[~2016-02-25 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 20:26 [PATCH v2 0/9] x86/xsaves: Fix XSAVES known issues Yu-cheng Yu
2016-02-25 20:26 ` [PATCH v2 1/9] x86/xsaves: Define and use user_xstate_size for xstate size in signal context Yu-cheng Yu
2016-02-25 20:26 ` [PATCH v2 2/9] x86/xsaves: Rename xstate_size to kernel_xstate_size to explicitly distinguish xstate size in kernel from user space Yu-cheng Yu
2016-02-25 20:26 ` [PATCH v2 3/9] x86/xsaves: Keep init_fpstate.xsave.header.xfeatures as zero for init optimization Yu-cheng Yu
2016-02-25 20:26 ` [PATCH v2 4/9] x86/xsaves: Introduce a new check that allows correct xstates copy from kernel to user directly Yu-cheng Yu
2016-02-25 20:26 ` [PATCH v2 5/9] x86/xsaves: Align xstate components according to CPUID Yu-cheng Yu
2016-02-25 20:26 ` [PATCH v2 6/9] x86/xsaves: Supervisor state component offset Yu-cheng Yu
2016-02-25 20:26 ` [PATCH v2 7/9] x86/xsaves: Fix PTRACE frames for XSAVES Yu-cheng Yu
2016-02-25 20:26 ` [PATCH v2 8/9] x86/xsaves: Fix XSTATE component offset print out Yu-cheng Yu
2016-02-25 20:26 ` [PATCH v2 9/9] x86/xsaves: Re-enable XSAVES Yu-cheng Yu
2016-02-25 20:34 ` Dave Hansen
2016-02-25 21:03 ` Yu-cheng Yu
2016-02-25 20:57 ` [PATCH v2 0/9] x86/xsaves: Fix XSAVES known issues Dave Hansen
2016-02-25 21:07 ` Yu-cheng Yu [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=20160225210715.GA8948@test-lenovo \
--to=yu-cheng.yu@intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=ravi.v.shankar@intel.com \
--cc=sai.praneeth.prakhya@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.