From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Gabriele Moabiti <gabmoa@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] floating point (int 16) exception
Date: Fri, 31 Oct 2008 17:31:43 +0100 [thread overview]
Message-ID: <490B32EF.8050503@domain.hid> (raw)
In-Reply-To: <857546.30206.qm@domain.hid>
Gabriele Moabiti wrote:
> Scenario: Xenomai 2.4.5, kernel 2.6.24-7 (x86) I have successfully
> trapped and restored int #0 (it is not reported in the example). Now
> I want to trap fpu exceptions (#16) of a Xenomai user task (ring 3).
>
> xfpu_xcpt.c -> kernel module used to intercept and manage fpu (#16)
> exceptions. xfpu_user.c -> xenomai user task
>
> The easiest way (it will not be so easy the final fpu exception
> manager of course!) to do this I knows was to do an fnclex but the
> example doesn't work (it hangs shortly). I have tried *many*
> solutions but nothing works. I think the problem is I can't do a
> simple fnclex but I can't figure how to solve the problem.
No, simply doing an fnclex will not do the trick.
If you do not know the details of Xenomai and Linux FPU handling on x86,
I advise you to let xenomai handle the fault, it does it without
switching to secondary mode, so, you can use it. I do not want to
explain you how it works because it is rather hairy, so, the only way to
understand, if you really want to, is to read the xenomai and linux
relevant sources.
--
Gilles.
next prev parent reply other threads:[~2008-10-31 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 16:26 [Xenomai-help] floating point (int 16) exception Gabriele Moabiti
2008-10-31 16:31 ` Gilles Chanteperdrix [this message]
2008-10-31 16:47 ` Gabriele Moabiti
2008-10-31 16:52 ` Gilles Chanteperdrix
2008-10-31 17:15 ` Gabriele Moabiti
2008-10-31 17:20 ` Gilles Chanteperdrix
2008-10-31 18:41 ` Gabriele Moabiti
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=490B32EF.8050503@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=gabmoa@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.