From: Yu-cheng Yu <yu-cheng.yu@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, 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 v3 9/9] x86/xsaves: Re-enable XSAVES
Date: Tue, 1 Mar 2016 16:58:18 -0800 [thread overview]
Message-ID: <20160302005818.GA30963@test-lenovo> (raw)
In-Reply-To: <A7390A91-7A02-4F5C-AFCE-375F49039361@zytor.com>
On Tue, Mar 01, 2016 at 04:53:53PM -0800, H. Peter Anvin wrote:
> Differences between i386 and x86-64 generally add problems, so unless this requires significant 32-bit-specific code we should not exclude i386 just because.
I have not seen any issues with 32-bit code, but will do some tests.
Thanks.
Yu-cheng
prev parent reply other threads:[~2016-03-02 1:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 17:41 [PATCH v3 0/9] x86/xsaves: Fix XSAVES known issues Yu-cheng Yu
2016-02-29 17:41 ` [PATCH v3 1/9] x86/xsaves: Define and use user_xstate_size for xstate size in signal context Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 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-29 17:42 ` [PATCH v3 3/9] x86/xsaves: Keep init_fpstate.xsave.header.xfeatures as zero for init optimization Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 4/9] x86/xsaves: Introduce a new check that allows correct xstates copy from kernel to user directly Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 5/9] x86/xsaves: Align xstate components according to CPUID Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 6/9] x86/xsaves: Supervisor state component offset Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 7/9] x86/xsaves: Fix PTRACE frames for XSAVES Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 8/9] x86/xsaves: Fix XSTATE component offset print out Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 9/9] x86/xsaves: Re-enable XSAVES Yu-cheng Yu
2016-03-01 23:56 ` Dave Hansen
2016-03-02 0:34 ` Yu-cheng Yu
2016-03-02 0:45 ` Dave Hansen
2016-03-02 0:48 ` Yu-cheng Yu
2016-03-02 0:53 ` H. Peter Anvin
2016-03-02 0:58 ` 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=20160302005818.GA30963@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox