[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <488FA318.3040905@zytor.com>
Date: Tue, 29 Jul 2008 16:09:12 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Suresh Siddha <suresh.b.siddha@...el.com>
CC: mingo@...e.hu, tglx@...utronix.de, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, arjan@...ux.intel.com,
roland@...hat.com, drepper@...hat.com, mikpe@...uu.se,
chrisw@...s-sol.org, andi@...stfloor.org,
linux-kernel@...r.kernel.org
Subject: Re: [patch 0/9] x86, xsave: xsave/xrstor support
Suresh Siddha wrote:
> This patchset adds the support for xsave/xrstor infrastructure for x86.
> xsave/xrstor manages the existing and future processor extended states in x86
> architecutre.
>
> More info on xsave/xrstor can be found in the Intel SDM's located at
> http://www.intel.com/products/processor/manuals/index.htm
>
> The layout of the xsave/xrstor area extends from the 512-byte FXSAVE/FXRSTOR
> layout. xsave/xrstor area layout consists of:
>
> - fxsave/fxrstor area (512 bytes)
> - xsave header area (64 bytes)
> - set of save areas, each corresponding to a processor extended state
>
> The number of save areas, the offset and the size of each save area is
> enumerated by CPUID leaf function 0xd.
>
> This patch includes the basic xsave/xrstor infrastructure(supporting FP/SSE),
> which includes:
> - context switch support, extending traditional lazy restore mechanism
> - signal handling support, extending(using the software reserved bytes
> 464..511 in the current 512byte layout of fxsave frame) the memory
> layout pointed out by the fpstate pointer in the sigcontext
>
> More details in the patches to follow.
>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@...el.com>
Applied as tip:x86/xsave.
I should warn I had to do quite a bit of manual fixup in order to
disentangle it from other changes in -tip, so please test it out; I
compile-tested it but for obvious reasons can't do more than that at the
moment.
-hpa
--
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