archive mirror
 help / color / mirror / Atom feed
From: Norbert Lange <>
Subject: Using lttng-ust with xenomai
Date: Fri, 22 Nov 2019 10:14:42 +0100	[thread overview]
Message-ID: <CADYdroN-i9yrpd-wjPSW36GUptRV+kOCJT=Yv6+Z5sCVBmo_SQ__33596.4964747959$1574414113$gmane$> (raw)


I already started a thread over at [1], but I guess its
more efficient to ask here aswell.
The basic concept is that xenomai thread run *below* Linux (threads
and irg handlers), which means that xenomai threads must not use any
linux services like the futex syscall or socket communication.

## tracepoints

expecting that tracepoints are the only thing that should be used from
the xenomai threads, is there anything using linux services.
the "bulletproof" urcu apparently does not need anything for the
reader lock (aslong as the thread is already registered), but I dont
know how the write-buffers are prepared.

You can call linux sycalls from xenomai threads (it will switch to the
linux shadow thread for that and lose realtime characteristics), so a
one time setup/shutdown like registering the threads is not an issue.

## membarrier syscall

I haven't got an explanation yet, but I believe this syscall does
nothing to xenomai threads (each has a shadow linux thread, that is
*idle* when the xenomai thread is active).
liburcu has configure options allow forcing the usage of this syscall
but not disabling it, which likely is necessary for Xenomai.

Any input is welcome.
Kind regards, Norbert

[1] -

             reply	other threads:[~2019-11-22  9:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22  9:14 Norbert Lange [this message]
     [not found] <>
2019-11-22 15:42 ` Using lttng-ust with xenomai Mathieu Desnoyers
     [not found] ` <>
2019-11-22 15:52   ` Jan Kiszka
     [not found]   ` <>
2019-11-22 17:01     ` Mathieu Desnoyers
     [not found]     ` <>
2019-11-22 17:36       ` Jan Kiszka
2019-11-22 17:44     ` Norbert Lange
     [not found]     ` <>
2019-11-22 17:52       ` Jan Kiszka
     [not found]       ` <>
2019-11-22 18:01         ` Norbert Lange
     [not found]         ` <>
2019-11-22 18:07           ` Jan Kiszka
     [not found]           ` <>
2019-11-22 21:38             ` Norbert Lange
2019-11-22 19:00       ` Mathieu Desnoyers
     [not found]       ` <>
2019-11-22 19:57         ` Norbert Lange
     [not found]         ` <>
2019-11-22 20:15           ` Mathieu Desnoyers
2019-11-22 17:55   ` Norbert Lange
     [not found]   ` <>
2019-11-22 19:03     ` Mathieu Desnoyers
     [not found]     ` <>
2019-11-22 20:04       ` Norbert Lange

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADYdroN-i9yrpd-wjPSW36GUptRV+kOCJT=Yv6+Z5sCVBmo_SQ__33596.4964747959$1574414113$gmane$' \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).