public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Zick" <lkml@morethan.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	"Thomas Gleixner <tglx@linutronix.de> Suresh Siddha" 
	<suresh.siddha@intel.com>, Tejun Heo <tj@kernel.org>,
	Venkatesh Pallapadi <venkatesh.pallapadi@intel.com>,
	Zhang Rui <rui.zhang@intel.com>
Subject: Re: [GIT PULL] x86 fixes for 2.6.30-rc8
Date: Sat, 30 May 2009 15:32:28 -0500	[thread overview]
Message-ID: <200905301532.30450.lkml@morethan.org> (raw)
In-Reply-To: <4A2187BF.1070205@zytor.com>

On Sat May 30 2009, H. Peter Anvin wrote:
> Michael S. Zick wrote:
> > On Sat May 30 2009, Pavel Machek wrote:
> >> Hi!
> >>
> >>> --- a/Documentation/kernel-parameters.txt
> >>> +++ b/Documentation/kernel-parameters.txt
> >>> @@ -1535,6 +1535,10 @@ and is between 256 and 4096 characters. It is defined in the file
> >>>  			register save and restore. The kernel will only save
> >>>  			legacy floating-point registers on task switch.
> >>>  
> >>> +	noxsave		[BUGS=X86] Disables x86 extended register state save
> >>> +			and restore using xsave. The kernel will fallback to
> >>> +			enabling legacy floating-point and sse state.
> >>> +
> >> Does that mean apps using sse8 will see their registers corrupted if
> >> this option is used? Or are new registers sets always added in a way
> >> that kernel has to enable them first?
> 
> New register sets always require enabling.
> 
> > Has this change been tested on the processors that have independent ftp&sse
> > units, without the shared registers?  Such as the VIA C7-M?
> 
> x87 and SSE are always separate.  Whether or not register sets are
> separate is an architectural issue, and isn't subject to variation
> across CPUs.
> 

In this case they are but I am glad to hear that Intel and VIA Tech.
are working this closely together.  It simplifies the support issues.

Mike
> 	-hpa
> 



      reply	other threads:[~2009-05-30 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 20:03 [GIT PULL] x86 fixes for 2.6.30-rc8 H. Peter Anvin
2009-05-25 22:50 ` Linus Torvalds
2009-05-25 22:51   ` Linus Torvalds
2009-05-25 23:03     ` H. Peter Anvin
2009-05-26 17:33       ` Pallipadi, Venkatesh
2009-05-25 23:02   ` H. Peter Anvin
2009-05-30 11:22 ` Pavel Machek
2009-05-30 12:13   ` Michael S. Zick
2009-05-30 19:23     ` H. Peter Anvin
2009-05-30 20:32       ` Michael S. Zick [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=200905301532.30450.lkml@morethan.org \
    --to=lkml@morethan.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@ucw.cz \
    --cc=rui.zhang@intel.com \
    --cc=suresh.siddha@intel.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=venkatesh.pallapadi@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