[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200905300713.23741.lkml@morethan.org>
Date: Sat, 30 May 2009 07:13:21 -0500
From: "Michael S. Zick" <lkml@...ethan.org>
To: Pavel Machek <pavel@....cz>
Cc: "H. Peter Anvin" <hpa@...or.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>,
"Thomas Gleixner <tglx@...utronix.de> Suresh Siddha"
<suresh.siddha@...el.com>, Tejun Heo <tj@...nel.org>,
Venkatesh Pallapadi <venkatesh.pallapadi@...el.com>,
Zhang Rui <rui.zhang@...el.com>
Subject: Re: [GIT PULL] x86 fixes for 2.6.30-rc8
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?
>
Has this change been tested on the processors that have independent ftp&sse
units, without the shared registers? Such as the VIA C7-M?
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists