All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dmitry Adamushko" <dmitry.adamushko@domain.hid>
To: Markus.Franke@domain.hid
Cc: Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] CONFIG_PREEMPT & irqbench
Date: Wed, 14 Feb 2007 13:10:56 +0100	[thread overview]
Message-ID: <b647ffbd0702140410r14617bdbt58f60cd9049c52af@domain.hid> (raw)
In-Reply-To: <45D2E86C.2010200@domain.hid>

On 14/02/07, Markus Franke <Markus.Franke@domain.hid> wrote:
> Jan Kiszka wrote:
> > Of course, irqloop runs in *primary* mode to be able to handle the
> > events deterministically. So it is not directly affected by CONFIG_PREEMPT.
>
> If I start irqloop in User-Mode, a thread is simply created via Linux
> system call pthread_create() which interacts with the
> xeno_irqbench-driver via ioctl(). But then I don't understand why
> irqloop is running in Primary (Xenomai) Mode? Because of the interaction
> with the RTDM-based driver?
> I am just wondering because I can't see something like rt_task_create().

There is life beyond the native skin. e.g. the posix one.

After all, Xenomai is all about skins (layers implementing various RT
API interfaces).

So pthread_create() as well as ioctl() you may see in irqloop are
implemented ("shadowed") by the posix skin.


-- 
Best regards,
Dmitry Adamushko


  reply	other threads:[~2007-02-14 12:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  0:01 [Xenomai-help] CONFIG_PREEMPT & irqbench Markus Franke
2007-02-14  8:53 ` Jan Kiszka
2007-02-14  9:00   ` Jan Kiszka
2007-02-14  9:59     ` Markus Franke
2007-02-14 10:17       ` Jan Kiszka
2007-02-14  9:59   ` Markus Franke
2007-02-14 10:28     ` Jan Kiszka
2007-02-14 10:46       ` Markus Franke
2007-02-14 12:10         ` Dmitry Adamushko [this message]
2007-02-14 12:54           ` Markus Franke
2007-02-14 12:22         ` Jan Kiszka

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=b647ffbd0702140410r14617bdbt58f60cd9049c52af@domain.hid \
    --to=dmitry.adamushko@domain.hid \
    --cc=Markus.Franke@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.