All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriele Moabiti <gabmoa@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] trap exceptions in user
Date: Wed, 8 Oct 2008 10:34:46 +0000 (GMT)	[thread overview]
Message-ID: <563071.90718.qm@domain.hid> (raw)

[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]



>I think you are traping yourself with impossible constraints.
>
>Anyway, the only way is register a custom exception handler using rthal
>functions. In your trap handler, you may wake up a user-space server
>thread which role is to handle exceptions (in user-space). This means that:
>- upon exception, you have a switch to the user-space server thread
>context, this will be slow;

Do I change rthal inside xenomai? How can I do?
Is there a benchmark or some number to understand better this slowness (in us)?

>- you have to rewrite the exception handling code, you can not rely
>on the exception handling code that was written in the assembly blob.
>
>I do not think it is a good idea to simply override the exception
>vectors, the kernel uses them, and you certainly want the kernel to
>continue working.
 
Yes I think so

Now SIS is about 500 kb of pure asm and works with a big cli on start and a sti
on finish @ring 0 and reprogram the exception vectors but I want to integrate into xenomai. 

Proposal:

- At start SIS save the addresses of the exception vectors
- When an exception is raised then the processor switch to the custom exception vectors but
  if the SIS is not currently active then jump to the old exception vectors

Is it possible?

Sorry for the large number of questions


      Scopri il blog di Yahoo! Mail:
Trucchi, novità e scrivi la tua opinione.
http://www.ymailblogit.com/blog

[-- Attachment #2: Type: text/html, Size: 2271 bytes --]

             reply	other threads:[~2008-10-08 10:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 10:34 Gabriele Moabiti [this message]
2008-10-08 10:50 ` [Xenomai-help] trap exceptions in user Gilles Chanteperdrix
  -- strict thread matches above, loose matches on Subject: below --
2008-10-24 19:17 Gabriele Moabiti
2008-10-26 23:49 ` Gilles Chanteperdrix
2008-10-24 15:30 Gabriele Moabiti
2008-10-24 13:53 Gabriele Moabiti
2008-10-24 17:43 ` Gilles Chanteperdrix
2008-10-24 17:44   ` Gilles Chanteperdrix
2008-10-15 15:30 Gabriele Moabiti
2008-10-15 15:39 ` Jan Kiszka
2008-10-14 10:01 Gabriele Moabiti
2008-10-14 10:21 ` Jan Kiszka
2008-10-14 12:13   ` Gilles Chanteperdrix
2008-10-13  9:55 Gabriele Moabiti
2008-10-11 19:32 Gabriele Moabiti
2008-10-11 19:34 ` Gilles Chanteperdrix
2008-10-11 21:35 ` Philippe Gerum
2008-10-10 17:57 Gabriele Moabiti
2008-10-10 16:02 Gabriele Moabiti
2008-10-10 16:04 ` Gilles Chanteperdrix
2008-10-11 11:24 ` Gilles Chanteperdrix
2008-10-10 15:24 Gabriele Moabiti
2008-10-10 15:38 ` Gilles Chanteperdrix
2008-10-10 13:50 Gabriele Moabiti
2008-10-10 14:00 ` Gilles Chanteperdrix
2008-10-08 11:32 Gabriele Moabiti
2008-10-08 12:29 ` Gilles Chanteperdrix
     [not found] <296620.67855.qm@domain.hid>
2008-10-08 10:09 ` Gilles Chanteperdrix
2008-10-03 12:30 Gabriele Moabiti
2008-10-03 14:58 ` Gilles Chanteperdrix

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=563071.90718.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.