From: Jan Kiszka <jan.kiszka@domain.hid>
To: adeos-main <adeos-main@gna.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] [PATCH 0/7] I-pipe fixes, cleanups, and enhancements
Date: Thu, 26 Apr 2007 20:39:38 +0200 [thread overview]
Message-ID: <4630F1EA.8020206@domain.hid> (raw)
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
Hi,
before ipipe-git gets busy again with work on 2.6.21, I'd like to flush
my patch queue. Here is an overview:
1. Build fix for the tracer over x86_64
2. Fix for Linux IRQ state during x86_64 boot
3. [JANITOR] Fix whitespace damages in the tracer
4. [JANITOR] Minor cleanups in ipipe/core.c
5. Extract minimal, dependency-free linux/ipipe_base.h from main
ipipe.h
6. Optimise __ipipe_stall_root, __ipipe_test_root, and
__ipipe_test_and_stall_root for execution on UP (only i386 and
x86_64 so far). This should improve Linux performance over I-pipe,
at least it did with the original version I posted last year.
7. Detect illicit cross-domain calls down the pipeline. Together with
the included Linux instrumentation, this can help to diagnose broken
RT code in the kernel, namely in drivers and skins. Might be of some
interest for RTDM hackers as recent user postings demonstrated...
All patches are against 2.6.20 (i386-1.7-03 / x86_64-1.0.06) and were
(as usual) quickly tested with Xenomai trunk on qemu boxes.
[Note that just this initial mail is CC'ed to xenomai-core, check
adeos-main for the actually patches.]
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next reply other threads:[~2007-04-26 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 18:39 Jan Kiszka [this message]
2007-04-30 15:55 ` [Xenomai-core] [PATCH 0/7] I-pipe fixes, cleanups, and enhancements Philippe Gerum
2007-05-02 9:15 ` Philippe Gerum
2007-05-02 9:15 ` Jan Kiszka
2007-05-02 9:25 ` Philippe Gerum
2007-05-02 9:16 ` Philippe Gerum
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=4630F1EA.8020206@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--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.