From: Avi Kivity <avi@argo.co.il>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: FP in kernelspace
Date: Sun, 30 Jul 2006 17:40:10 +0300 [thread overview]
Message-ID: <44CCC4CA.6000208@argo.co.il> (raw)
In-Reply-To: <44CC97A4.8050207@gmail.com>
Jiri Slaby wrote:
>
> Hello,
>
> I have a driver written for 2.4 + RT patches with FP support. I want
> it to work
> in 2.6. How to implement FP? Has anybody developped some "protocol"
> between KS
> and US yet? If not, could somebody point me, how to do it the best --
> with low
> latency.
> The device doesn't generate irqs *), I need to quickly respond to
> timer call,
> because interval between two posts of data to the device has to be
> equal as much
> as possible (BTW is there any way how to gain up to 5000Hz).
> I've one idea: have a thread with RT priority and wake the app in US
> waiting in
> read of character device when timer ticks, post a struct with 2 floats
> and
> operation and wait in write for the result. App computes, writes the
> result, we
> are woken and can post it to the device. But I'm afraid it would be
> tooo slow.
>
> *) I don't know how to persuade it (standard PLX chip with unknown
> piece of
> logic behind) to generate, because official driver is closed and _very_
> expensive. Old (2.4) driver was implemented with RT thread and timer,
> where FP
> is implemented within RT and computed directly in KS.
>
> So 2 questions are:
> 1) howto FP in kernel
>
kernel_fpu_begin();
c = d * 3.14;
kernel_fpu_end();
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2006-07-30 14:40 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 [this message]
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
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=44CCC4CA.6000208@argo.co.il \
--to=avi@argo.co.il \
--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