Date: Sat, 15 May 2010 14:41:12 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Marius Strobl <marius@alchemy.franken.de> Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: AESNI driver and fpu_kern KPI Message-ID: <20100515114112.GU83316@deviant.kiev.zoral.com.ua> In-Reply-To: <20100515110436.GA7224@alchemy.franken.de> References: <20100515100401.GT83316@deviant.kiev.zoral.com.ua> <20100515110436.GA7224@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--FxsMg9mYBDvYslEH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 15, 2010 at 01:04:36PM +0200, Marius Strobl wrote: > On Sat, May 15, 2010 at 01:04:01PM +0300, Kostik Belousov wrote: > >=20 > > I am interested in the problem reports and reviews. Maintainers of > > !x86-oids are welcome to provide feedback whether they feel that > > proposed KPI could be implemented on their architectures, or what > > modifications they consider as needed to be able to implement > > it. > >=20 >=20 > FYI, sparc64 doesn't need such a KPI as it supports using the FPU > in kernel unconditionally for ages. How is this done on sparc64 ? Is PSTATE.PEF cleared on kernel entry, or FPU is disabled ? When I researched the problem space, I noted that windows on amd64 also provides an unrestricted access to XMM, while not on i386: http://msdn.microsoft.com/en-us/library/ff545910%28VS.85%29.aspx It seems that windows unconditionally set CR0.TS on kernel-mode entry from usermode. --FxsMg9mYBDvYslEH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkvuiFgACgkQC3+MBN1Mb4iqgQCgnDzTLp4J2jRphSsSifiVIg7v mRgAnR+dB+TuJYppy1w/D7WR7ngbr1bS =xSd4 -----END PGP SIGNATURE----- --FxsMg9mYBDvYslEH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100515114112.GU83316>