All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Nazarov Sergey <s-nazarov@domain.hid>
Cc: Adeos <adeos-main@gna.org>
Subject: Re: [Adeos-main] Interrupt handling problem on Compulab EM-X270.
Date: Thu, 24 Feb 2011 13:37:25 +0100	[thread overview]
Message-ID: <4D665105.8040107@domain.hid> (raw)
In-Reply-To: <41131298550043@domain.hid>

Nazarov Sergey wrote:
> Test:
> non-RT load: dd if=/dev/zero of=/dev/null + ping flud from another host,
> RT-load: 3 latency tests (user, kernel and timer task) + switchtest,
> worked for 1 hour without visible problems (0% of ping packets lost).
>    Sergey.

Ok. The problem is that on some machines, we get a lockup when using the
edge handler, because the edge handler does not mask the interrupt line,
and so the interrupt triggers again. I guess this must happens with
devices having a level semantic.

But anyway, I prefer some non real-time interrupts lost, than a complete
lockup, so, the code will stay the way it is, I suggest you modify the
board/driver code to change the flow handler of only the line you use.
This change could be integrated into the I-pipe patch.

-- 
                                                                Gilles.


      parent reply	other threads:[~2011-02-24 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 20:10 [Adeos-main] Interrupt handling problem on Compulab EM-X270 Nazarov Sergey
2011-02-22 20:21 ` Gilles Chanteperdrix
     [not found]   ` <437861298457092@domain.hid>
     [not found]     ` <4D64E2A4.7080105@domain.hid>
     [not found]       ` <661661298458316@domain.hid>
     [not found]         ` <4D64E810.4040005@domain.hid>
     [not found]           ` <549401298459119@domain.hid>
     [not found]             ` <4D64F94E.5040407@domain.hid>
     [not found]               ` <41131298550043@domain.hid>
2011-02-24 12:37                 ` Gilles Chanteperdrix [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=4D665105.8040107@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=adeos-main@gna.org \
    --cc=s-nazarov@domain.hid \
    /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.