public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Dave Hansen <dave.hansen@intel.com>,
	Asit K Mallick <asit.k.mallick@intel.com>,
	Glenn Williamson <glenn.p.williamson@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH v3 Bugfix 0/6] xstate/fpu bug fixes
Date: Sat, 9 May 2015 08:09:59 +0200	[thread overview]
Message-ID: <20150509060959.GB4156@gmail.com> (raw)
In-Reply-To: <1431120665-36841-1-git-send-email-fenghua.yu@intel.com>


* Fenghua Yu <fenghua.yu@intel.com> wrote:

> From: Fenghua Yu <fenghua.yu@intel.com>
> 
> This patchset is supposed to fix some xsave/xsaves/fpu related issues.

So as I mentioned it to Dave Hansen already yesterday, I think the 
right, easily backportable fix would be to switch the kernel to 
'standard format'. It's very close to the compacted format and its 
behavior is much more obvious and it doesn't change the context size 
on us.

Then, on top of a known working kernel, we can re-introduce compacted 
format without pressure, with all the necessary signal frame 
conversion problems solved properly.

Thanks,

	Ingo

      parent reply	other threads:[~2015-05-09  6:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 21:30 [PATCH v3 Bugfix 0/6] xstate/fpu bug fixes Fenghua Yu
2015-05-08 21:31 ` [PATCH v3 Bugfix 1/6] x86/xsave.c: Fix xstate offsets and sizes enumeration Fenghua Yu
2015-05-08 21:31 ` [PATCH v3 Bugfix 2/6] x86/xsaves: Define and use user_xstate_size for xstate size in signal context Fenghua Yu
2015-05-08 21:31 ` [PATCH v3 Bugfix 3/6] x86/xsaves: Rename xstate_size to kernel_xstate_size to explicitly distinguish xstate size in kernel from user space Fenghua Yu
2015-05-08 21:31 ` [PATCH v3 Bugfix 4/6] x86/xsave: Don't add new states in xsave_struct Fenghua Yu
2015-05-08 21:31 ` [PATCH v3 Bugfix 5/6] x86/xsaves: Keep xstate_bv in init_xstate_buf header as zero for init optimimization Fenghua Yu
2015-05-08 21:31 ` [PATCH v3 Bugfix 6/6] x86/xsave.c: Introduce a new check that allows correct xstates copy from kernel to user directly Fenghua Yu
2015-05-09  6:09 ` Ingo Molnar [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=20150509060959.GB4156@gmail.com \
    --to=mingo@kernel.org \
    --cc=asit.k.mallick@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=glenn.p.williamson@intel.com \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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