All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] [RFC][PATCH 0/2] user space rt-safe printing and tracing
Date: Sat, 17 Feb 2007 10:02:31 +0100	[thread overview]
Message-ID: <45D6C4A7.6090707@domain.hid> (raw)

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

Hi,

fresh from the development labs, guaranteed to be incomplete and lightly
tested, here comes a patch series that addresses two issues bugging me
(and maybe others) for quite some time:

 1. How to print from RT (primary) context without stepping down to
    secondary mode?

 2. How to trace Xenomai syscalls without hacking on strace _and_
    I-pipe (ptrace for RT-syscalls) _and_ without suffering from its
    temporal intrusiveness (traced processes are stopped while examining
    their syscall arguments)?

The following two patches (against trunk) aim at answering both
questions. The first one provides a generic rtprint library, the second
one exploits it by instrumenting ridiculous subsets of libnative and
libpthread_rt. Find details on design and usage will be found in the
following mails.

Take this series as food for discussion about its usefulness, code
organisation and remaining quirks, and also as an offer to early
adopters. While I think that librtprint should be generally acceptable,
I would like to gain some comments on my approach for per-process
syscall tracing (and its impact on the skin libraries) first. Then, if
this tracing is considered viable, helping hands for the boooooring
instrumentation work would be *very* welcome!

Jan


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

                 reply	other threads:[~2007-02-17  9:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=45D6C4A7.6090707@domain.hid \
    --to=jan.kiszka@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.