All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: poornima r <rpoornar@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] [Adeos-main] EBUSY error with rt_intr_create API for timer interrupt
Date: Mon, 01 Oct 2007 20:42:55 +0200	[thread overview]
Message-ID: <47013FAF.8040306@domain.hid> (raw)
In-Reply-To: <330902.482.qm@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

poornima r wrote:
> Hello,
> 
> I am trying to register an handler for the timer
> interrupt with the following call in my init_module()
> (kernel space) for xenomai domain.
> 
> err = 
> rt_intr_create(&intr_desc,"ir-xenomai",TIMER_INTERRUPT,
> &ir_handler,NULL, I_SHARED);

Xenomai questions are better addressed to Xenomai mailing lists. I moved
this thread therefore.

>  
> When I try inseting my module, I get EBUSY error.
> 
> Is there any problem with the interrupt object
> creation mode (I_SHARED)?
> Why is this error when interrupts can be shared
> between 
> Xenomai and Linux?

Generally, sharing IRQs between the RT and the non-RT (Linux) domain is
a very tricky thing that quickly makes your box instable or at least
indeterministic.

Specifically for sharing the timer IRQ, the Xenomai with the help of the
I-pipe patch provides fine APIs so that you don't need to mess with
internals, just have a look at the docs. Because Xenomai already manages
the timer IRQ in the RT domain, rt_intr_create denies the access.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]

      reply	other threads:[~2007-10-01 18:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25 15:09 [Adeos-main] EBUSY error with rt_intr_create API for timer interrupt poornima r
2007-10-01 18:42 ` Jan Kiszka [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=47013FAF.8040306@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=rpoornar@domain.hid \
    --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.