From: Dave Hansen <dave.hansen@linux.intel.com>
To: Borislav Petkov <bp@suse.de>, Yu-cheng Yu <yu-cheng.yu@intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Andy Lutomirski <luto@kernel.org>,
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 v7 00/13] x86/xsaves: Fix XSAVES issues
Date: Wed, 11 May 2016 13:14:03 -0700 [thread overview]
Message-ID: <5733928B.7030909@linux.intel.com> (raw)
In-Reply-To: <20160511200436.GP2180@pd.tnic>
On 05/11/2016 01:04 PM, Borislav Petkov wrote:
> On Wed, May 11, 2016 at 12:51:03PM -0700, Yu-cheng Yu wrote:
>> XSAVES is a kernel-mode instruction. It offers a compacted format and
>> memory-write optimization. These patches fix issues in the first
>> implementation.
>
> do you even read my emails?!
>
> https://lkml.kernel.org/r/20160511041741.GB2180@pd.tnic
>
> That's the third patchset in three days! What's with the spamming?!
Borislav, if you don't want to be cc'd on these patches, then please
speak up. I'm sure Yu-cheng would be happy not to cc you.
But, seriously, he's churning through, responding to feedback and
improving the patches quickly. I only wish most patch authors did this.
And, despite breaking it up into 13 pieces, there is *NOT* a lot of
code here. There's no sane reason to wait a week between iterations.
I encouraged Yu-cheng to keep up with the current pace and not wait a
week between reposts, despite what you requested. Sorry. Just speak up
if you want off the cc.
next prev parent reply other threads:[~2016-05-11 20:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 19:51 [PATCH v7 00/13] x86/xsaves: Fix XSAVES issues Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 01/13] x86/xsaves: Define and use fpu_user_xstate_size Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 02/13] x86/xsaves: Rename xstate_size to fpu_kernel_xstate_size to distinguish from fpu_user_xstate_size Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 03/13] x86/xsaves: Keep init_fpstate.xsave.header.xfeatures as zero for init optimization Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 04/13] x86/xsaves: Introduce a new check that allows correct xstates copy from kernel to user directly Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 05/13] x86/xsaves: Align xstate components according to CPUID Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 06/13] x86/xsaves: Supervisor state component offset Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 07/13] x86/xsaves: Fix PTRACE frames for XSAVES Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 08/13] x86/xsaves: Fix XSTATE component offset print out Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 09/13] x86/xsaves: Fix xstate_offsets, xstate_sizes for non-extended states Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 10/13] x86/xsaves: Fix __fpu_restore_sig() for XSAVES Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 11/13] x86/xsaves: When a disabled xstate component address is requested, return NULL Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 12/13] x86/xsaves: Fix fpstate_init() for XRSTORS Yu-cheng Yu
2016-05-11 19:51 ` [PATCH v7 13/13] x86/xsaves: Re-enable XSAVES Yu-cheng Yu
2016-05-11 20:04 ` [PATCH v7 00/13] x86/xsaves: Fix XSAVES issues Borislav Petkov
2016-05-11 20:14 ` Dave Hansen [this message]
2016-05-11 20:34 ` Borislav Petkov
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=5733928B.7030909@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=bp@suse.de \
--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 \
--cc=yu-cheng.yu@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 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.