All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jesper Christensen <jbc@thrane.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Lost interrupts
Date: Wed, 24 Apr 2013 09:52:36 +0200	[thread overview]
Message-ID: <51778F44.8030109@siemens.com> (raw)
In-Reply-To: <51778C38.8030105@thrane.com>

On 2013-04-24 09:39, Jesper Christensen wrote:
> On 04/23/2013 02:19 PM, Jan Kiszka wrote:
>> On 2013-04-23 11:22, Jesper Christensen wrote:
>>> Hi guys
>>>
>>> I have a quick question regarding rtdm synchronisation. Is it possible
>>> to "loose" an interrupt if it is generated while i am inside a critical
>>> section protected by a rtdm_lock_get_irqsave/rtdm_lock_put_irqrestore?
>> Nope, as Gilles already answered.
>>
>>> I have a problem with an ethernet driver where the Tx Queue fills up and
>>> i suspect that its because the Tx ISR isn't being executed for the above
>>> mentioned reason.
>> Are we talking about a Linux NIC or a real-time device? What is your
>> software stack in general (used components and their versions)?
>>
>> Jan
>>
> 
> Its a real time device (ETSEC on a MPC8520) with xenomai 2.5.6 on a
> linux-2.6.29.6 and ipipe-2.7-04 and the stack is rtnet-0.9.12. The ipipe
> patch has minor modifications to make it apply to the freescale patched
> version of the linux source. The rtnet source also has several (heavier)
> modifications (scattered skbs, etc.).

That introduces a lot of variations and potential breakage points. You
will have to debug through them.

> 
> So if an interrupt occurs during a critical section, the ISR will run
> upon exit from that section?

Critical RT sections disable interrupts in hardware. And common CPUs
keep interrupts pending that arrive while delivery is disabled,
replaying them once the OS reenables them again.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2013-04-24  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23  9:22 [Xenomai] Lost interrupts Jesper Christensen
2013-04-23 11:21 ` Gilles Chanteperdrix
2013-04-23 12:19 ` Jan Kiszka
2013-04-24  7:39   ` Jesper Christensen
2013-04-24  7:52     ` Jan Kiszka [this message]
2013-04-24  8:21       ` Jesper Christensen
2013-04-24  7:39   ` Jesper Christensen

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=51778F44.8030109@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=jbc@thrane.com \
    --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.