All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Jan Kiszka <jan.kiszka@siemens.com>, xenomai@xenomai.org
Subject: Re: Mixing cobalt and alchemy?
Date: Wed, 06 Mar 2019 21:20:17 +0100	[thread overview]
Message-ID: <1763748.uoOIHctIBT@blindfold> (raw)
In-Reply-To: <bd50d09d-fe52-a7c5-c733-4d8ad50030bf@siemens.com>

Am Mittwoch, 6. März 2019, 18:25:56 CET schrieb Jan Kiszka:
> On 06.03.19 10:59, Richard Weinberger via Xenomai wrote:
> > Hi!
> > 
> > I have a Xenomai 2.6 application which makes heavy usage of
> > rt_dev_ioctl() and shadow threads
> > with rt_task_shadow().
> > 
> > If I understand the new Xenomai 3 API correctly, rt_dev_ioctl() for
> > userspace is gone and the cobalt wrappers should be used such that
> > plain ioctl() calls will be routed through libcobalt.
> > What I don't fully understand is how to mix these with the alchemy
> > skin such that the application can use rt_task_shadow() and friends
> > because the cobalt wrapper also wraps pthread_create().
> > The application simply does not fully fit in either cobalt nor alchemy skins.
> > 
> > Is it legal to modify lib/cobalt/cobalt.wrappers to wrap only read/close/ioctl?
> > Or can I directly issue cobalt syscalls from the application?
> > 
> 
> You can do __RT(ioctl(...)), that's also what the transition kit (trank) does to 
> provide rt_dev_ioctl.

Good to know!
Then I'll use alchemy and the __RT() wrappers.

Thanks,
//richard




      reply	other threads:[~2019-03-06 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  9:59 Mixing cobalt and alchemy? Richard Weinberger
2019-03-06 17:25 ` Jan Kiszka
2019-03-06 20:20   ` Richard Weinberger [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=1763748.uoOIHctIBT@blindfold \
    --to=richard@nod.at \
    --cc=jan.kiszka@siemens.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.