From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Ran Shalit <ranshalit@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Communication between RT-kernel to non-RT kernel
Date: Thu, 28 Apr 2016 12:52:36 +0200 [thread overview]
Message-ID: <20160428105236.GA10481@hermes.click-hack.org> (raw)
In-Reply-To: <CAJ2oMh+1yKWqQXWHoQELsD731xDGWWjiYvWNSXv5Nc=1Ky5xSQ@mail.gmail.com>
On Thu, Apr 28, 2016 at 08:37:17AM +0300, Ran Shalit wrote:
> On Thu, Apr 28, 2016 at 7:44 AM, Ran Shalit <ranshalit@gmail.com> wrote:
> > Hello,
> >
> > I am new with xenomai.
> >
> > I've made a lot of reading in the documentation which is very helpful.
> > But I haven't found how to communicate between rt kernel to non-rt
> > kernel on same machine,
> > Is there any example or documantation which explains this ?
> >
> > Best Regards,
> > Ran
>
> I guess that there is actually no need for such example or documentation.
> In userland 2 applications, one using xenomai kernel and the other
> linux kernel can commuicate
> in any method available in Linux between processes (pipes, shared
> memeory, etc) . Right?
Not quite. Accessing a pipe from a xenomai thread will cause it to
switch to secondary mode, IOW to migrate to the Linux kernel.
The IPC adapted to communicated between Xenomai threads and plain
Linux threads is XDDP, see the API documentation here:
https://xenomai.org/api-reference/
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2016-04-28 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 4:44 [Xenomai] Communication between RT-kernel to non-RT kernel Ran Shalit
2016-04-28 5:37 ` Ran Shalit
2016-04-28 10:52 ` Gilles Chanteperdrix [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-28 12:45 Ran Shalit
2016-04-29 19:38 ` Gilles Chanteperdrix
2016-04-30 11:45 ` Ran Shalit
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=20160428105236.GA10481@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=ranshalit@gmail.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.