public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: FP in kernelspace
Date: Sun, 30 Jul 2006 18:23:50 +0300	[thread overview]
Message-ID: <44CCCF06.4070406@argo.co.il> (raw)
In-Reply-To: <44CCCB74.9010605@gmail.com>

Jiri Slaby wrote:
>
> > unfortunately this only works for MMX not for real fpu (due to 
> exception
> > handling uglies)
>
> concludes it's not multiplatform at all... For that reasen I (maybe) 
> want some
> "protocol" for communication with US, where I can easily compute it.
>
Well, usually such a protocol is by means of read(2) and write(2) to a 
character device provided by your driver: userspace reads some data, 
does the fp ops, and writes it back.  If you want realtime you'll have 
to use a realtime thread with the appropriate priority.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2006-07-30 15:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30 11:28 FP in kernelspace Jiri Slaby
2006-07-30 11:31 ` Jiri Slaby
2006-07-30 14:32 ` Arjan van de Ven
2006-07-30 14:40 ` Avi Kivity
2006-07-30 14:54   ` Arjan van de Ven
2006-07-30 15:09     ` Jiri Slaby
2006-07-30 15:20       ` Arjan van de Ven
2006-07-30 15:23       ` Avi Kivity [this message]
2006-07-30 15:21     ` Avi Kivity
2006-07-30 17:34       ` Andi Kleen
2006-07-30 18:11         ` Avi Kivity
2006-07-30 18:15           ` Andi Kleen
2006-07-30 18:30             ` Avi Kivity
2006-07-30 18:17           ` Jan Engelhardt
2006-07-30 17:33     ` Andi Kleen
2006-07-30 18:18   ` Jan Engelhardt
2006-07-30 18:28     ` Avi Kivity
2006-07-30 23:11       ` Jan Engelhardt
2006-07-30 17:32 ` Andi Kleen
2006-07-31  0:33 ` Steven Rostedt

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=44CCCF06.4070406@argo.co.il \
    --to=avi@argo.co.il \
    --cc=arjan@infradead.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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