Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

freebsd-amd64 Digest, Vol 353, Issue 3

0 views
Skip to first unread message

freebsd-am...@freebsd.org

unread,
Mar 24, 2010, 8:00:15 AM3/24/10
to freebs...@freebsd.org
Send freebsd-amd64 mailing list submissions to
freebs...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
or, via email, send a message with subject or body 'help' to
freebsd-am...@freebsd.org

You can reach the person managing the list at
freebsd-a...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-amd64 digest..."


Today's Topics:

1. RE: XMM register usage in the kernel (Matthew Fleming)


----------------------------------------------------------------------

Message: 1
Date: Tue, 23 Mar 2010 13:40:01 -0700
From: "Matthew Fleming" <matthew...@isilon.com>
Subject: RE: XMM register usage in the kernel
To: "Kostik Belousov" <kost...@gmail.com>, <ar...@freebsd.org>,
<am...@freebsd.org>
Message-ID:
<06D5F9F6F655AD4C92E2...@seaxch09.desktop.isilon.com>
Content-Type: text/plain; charset="us-ascii"

> The KPI consists of two functions, fpu_kern_enter() and
fpu_kern_leave().
> The pair should brace the region of code that intend to use
coprocessor.
> Caller shall provide the context save area, I expect that usually this
> memory will be allocated as part of larger subsystem data structure.
>
> fpu_kern_enter() allows the nesting, assuming fpu_kern_leave() is
called
> proper number of times to pop the context stack.

Isilon would like it if something like this functionality ended up in
CURRENT. We have some hacks that do something similar. We use SSE2
instructions to significantly speed up computing ... stuff. :-)

Thanks,
matthew


------------------------------

End of freebsd-amd64 Digest, Vol 353, Issue 3
*********************************************

0 new messages