From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: adeos-main@gna.org, xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: [PATCH] latency tracer update
Date: Thu, 05 Jan 2006 12:15:07 +0100 [thread overview]
Message-ID: <43BCFFBB.1080303@domain.hid> (raw)
In-Reply-To: <43BCF891.1080402@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
Philippe Gerum wrote:
> Jan Kiszka wrote:
>
>> Hi again,
>>
>> here comes the first update of the new latency tracer.
>>
>> arch/i386/kernel/entry.S | 27 +++
>
>
> Is there any good reason to patch the callers of __ipipe_handle_irq
> instead of instrumenting the callee directly?
>
To capture the invocation delay of __ipipe_handle_irq itself.
>> arch/i386/kernel/ipipe-root.c | 4
>> include/asm-i386/system.h | 70 +++++++++
>> include/linux/ipipe_trace.h | 3
>> kernel/ipipe/Kconfig | 18 ++
>> kernel/ipipe/tracer.c | 247 +++++++++++++++++++++++-----------
>> 6 files changed, 288 insertions(+), 81 deletions(-)
>>
>
>
Meanwhile I found a solution for the described unterminated trace (put
an explicite trace_end at the end of __ipipe_unstall_iret_root),
included the irq number in the begin/end report, and stumbled over some
other remaining unterminated trace on a different machine. So, no need
to hurry with the merge (not the review! ;) ), I will publish a second
revision first.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2006-01-05 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 22:45 [Xenomai-core] [PATCH] latency tracer update Jan Kiszka
2006-01-05 10:13 ` [Xenomai-core] " Philippe Gerum
2006-01-05 10:44 ` Philippe Gerum
2006-01-05 11:15 ` Jan Kiszka [this message]
2006-01-06 10:04 ` Jan Kiszka
2006-01-06 19:39 ` Jan Kiszka
2006-01-07 13:35 ` Philippe Gerum
2006-01-06 11:31 ` [Xenomai-core] Re: [Adeos-main] " 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=43BCFFBB.1080303@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--cc=rpm@xenomai.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.