All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Mayer <h.mayer@domain.hid>
To: Kristian Benoit <kbenoit@domain.hid>
Cc: adeos-main@gna.org, Philippe Gerum <rpm@xenomai.org>
Subject: Re: [Fwd: [Adeos-main] LRTBF par-log.c & adeos_critical_enter question]
Date: Wed, 13 Jul 2005 23:35:39 +0200	[thread overview]
Message-ID: <42D5892B.8040805@domain.hid> (raw)
In-Reply-To: <1121261614.16275.15.camel@domain.hid>

Kristian Benoit wrote:
> On Tue, 2005-07-12 at 23:55 +0200, Hannes Mayer wrote:
> 
>>I mean, is it possible to get information on how many interrupts were
>>lost ?
> 
> 
> Just a though like that, that depend of what you want to do when you
> critical enter.
> 
> Suppose you have the domains root and ham. Where root is the Linux
> domain and ham is your domain that handle your interrupt. Then if you
> add the domain potatoes that is of higher priority than root and ham.
> You can suspend the domain potatoes most of the time, but when you stall
> (stalling instead of critical_enter is the key) the domain ham you can
> resume the domain potatoes that will count the number of interrupt
> receive upon reception of your interrupt. Then when you unstall the
> domain ham, you get the count from the domain potatoes and resuspend it.
> 
> Kristian

Thanks a lot Kristian and Philippe for your answers and tips!
I've got some good pointers now for further research!
If a day would just have 36 hours ;-)

Best regards,
Hannes.



      reply	other threads:[~2005-07-13 21:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42D2B3B7.30007@domain.hid>
2005-07-11 21:28 ` [Fwd: [Adeos-main] LRTBF par-log.c & adeos_critical_enter question] Kristian Benoit
2005-07-12 21:55   ` Hannes Mayer
2005-07-13  4:04     ` Kristian Benoit
2005-07-13  8:26     ` Philippe Gerum
2005-07-13 13:33     ` Kristian Benoit
2005-07-13 21:35       ` Hannes Mayer [this message]

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=42D5892B.8040805@domain.hid \
    --to=h.mayer@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=kbenoit@domain.hid \
    --cc=rpm@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.