All of lore.kernel.org
 help / color / mirror / Atom feed
From: stefano.franzoni@domain.hid
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] interrupt service routine issue
Date: Thu, 29 Jan 2009 17:51:31 +0100	[thread overview]
Message-ID: <20090129165132.2C8AE1C066@domain.hid> (raw)
In-Reply-To: <4981CDB7.5090905@domain.hid>

>if it is Linux's pthread_cond_signal, this is normal, if this is
>Xenomai's pthread_cond_signal, then we have a problem.

How can I verify this point?



                                                                           
             Gilles                                                        
             Chanteperdrix                                                 
             <gilles.chanteper                                          To 
             drix@domain.hid>         stefano.franzoni@domain.hid        
                                                                        cc 
             29/01/2009 16:39          "xenomai@xenomai.org"              
                                       <xenomai@xenomai.org>              
                                                                   Subject 
                                       Re: [Xenomai-help] interrupt        
                                       service routine issue               
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




stefano.franzoni@domain.hid wrote:
> Thanks Gilles,
>
> with your suggestion, setting the special mode bit T_WARNSW for the
> incriminated task, we found two critical functions that caused switches
to
> secondary mode.
>
> I report them for documentation:
>
> 1. We used mmap function used to map a file into memory. The access to
the
> memory caused sometimes the switch to secondary mode.

damn, this should not happen, we use mlockall and some additional tricks
in the I-pipe patch to avoid that.

> 2. A pthread_cond_signal call used to unlock a waiting task always
> generates the switch to secondary mode.

if it is Linux's pthread_cond_signal, this is normal, if this is
Xenomai's pthread_cond_signal, then we have a problem.

>
> We have implemented the two functions in a lower priority thread and the
> issue was solved.
> Thanks to your magic silver bullet!!
>
> To stress my application I have found a DoHell script by Ingo Molnar
> (http://marc.info/?l=linux-kernel&m=111947618802722&w=2) but it is
> uncompleted. Can you send your DoHell script?

I am afraid it is much the same. I have ltp installed in /ltp and do:

#! /bin/sh

mount | grep -q sda1 || mount /dev/sda1 /mnt
modprobe rtc-cmos

dortc() {
    chrt -f 98 -p `pidof 'IRQ 8'`
    /bin/rtc_wakeup -f 8192 -t 100000
}

run40() {
    while true; do ./runalltests.sh -x 40; done
}

while true; do dd if=/dev/zero of=/mnt/bigfile bs=1024000 count=100; done &
while true; do killall hackbench; sleep 5; done &
while true; do /ltp/testcases/bin/hackbench 20; done &
( cd /ltp; run40; ) &
ping -l 100000 -q -s 10 -f 192.168.0.5 &
while true; do ls -lR / > /dev/null 2>&1; done &
dortc &

--
                                                 Gilles.




  parent reply	other threads:[~2009-01-29 16:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 13:20 [Xenomai-help] interrupt service routine issue stefano.franzoni
2009-01-28 13:38 ` Gilles Chanteperdrix
2009-01-29 15:22   ` stefano.franzoni
2009-01-29 15:39     ` Gilles Chanteperdrix
2009-01-29 15:56       ` Jan Kiszka
2009-01-29 16:00         ` Gilles Chanteperdrix
2009-01-29 16:51       ` stefano.franzoni [this message]
2009-01-29 16:54         ` Gilles Chanteperdrix
2009-01-28 13:46 ` 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=20090129165132.2C8AE1C066@domain.hid \
    --to=stefano.franzoni@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.