From: Gabriele Moabiti <gabmoa@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] floating point (int 16) exception
Date: Fri, 31 Oct 2008 16:47:33 +0000 (GMT) [thread overview]
Message-ID: <327543.30247.qm@domain.hid> (raw)
In-Reply-To: 490B32EF.8050503@domain.hid
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
>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.
I need to manage exceptions in a different way of the x86 default so I have to unmask fpu exceptions. I have read and follow how it works but in xenomai fpu exceptions invoke a switch to linux...
int xnpod_trap_fault(xnarch_fltinfo_t *fltinfo)
{
...
if (xnpod_shadow_p()) {
...
xnshadow_relax(xnarch_fault_notify(fltinfo));
}
return 0;
}
so there is not in the source code an example on how to trap exception and remain into real time task...
Unisciti alla community di Io fotografo e video, il nuovo corso di fotografia di Gazzetta dello sport:
http://www.flickr.com/groups/iofotografoevideo
[-- Attachment #2: Type: text/html, Size: 1750 bytes --]
next prev parent reply other threads:[~2008-10-31 16:47 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
2008-10-31 16:47 ` Gabriele Moabiti [this message]
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=327543.30247.qm@domain.hid \
--to=gabmoa@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--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.