All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johann Obermayr <johann.obermayr@sigmatek.at>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: [Xenomai] xenomai , irq and pci
Date: Wed, 05 Mar 2014 17:22:28 +0100	[thread overview]
Message-ID: <53174F44.6000309@sigmatek.at> (raw)

Hello,

celeron dual core with PCIe - PCI bridge
we use kernel 3.10.xx smp with  (isolcpus=0)
smi is disabled.
xenomai 2.6.3

we have a pci card with a fpga (with irq) and sram.

we have 2 task running.

task0 is one high prior in primary domain on core0.
this task wait for event, that is fired by fpga irq.
than this task will make some pci accesses to the fpga.

the other task (task1) is a shadow task, but running in secondary domain 
on core 1.
This task make many big memcpy to sram.

in the ipipe_handler_irq we have a function callback.
a small driver hooks to this callback add make some tracepoint into
a shared memory.

with the trace we see some time a very high jitter in the ipipe_handler_irq
function (around 250 us).
has anyone an explanation for this?

and a 4 byte access from task0 to fpga need more than 300us,
  while task1 is writing to sram.

Thanks
   Johann




             reply	other threads:[~2014-03-05 16:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 16:22 Johann Obermayr [this message]
2014-03-05 16:41 ` [Xenomai] xenomai , irq and pci Gilles Chanteperdrix
2014-03-05 17:34   ` Gilles Chanteperdrix
2014-03-05 19:59     ` Jeroen Van den Keybus
2014-03-06 18:55       ` Johann Obermayr
2014-03-06  8:25   ` Johann Obermayr
2014-03-06 19:20     ` Gilles Chanteperdrix
2014-03-06 19:45       ` Johann Obermayr
     [not found]       ` <5318D021.8020802@sigmatek.at>
     [not found]         ` <5318D0B3.4020900@xenomai.org>
2014-03-06 19:53           ` Johann Obermayr

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=53174F44.6000309@sigmatek.at \
    --to=johann.obermayr@sigmatek.at \
    --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.