From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: adeos-main@gna.org
Subject: [Adeos-main] Re: Adeos-cvs Digest, Vol 10, Issue 11
Date: Wed, 26 Apr 2006 18:19:51 +0200 [thread overview]
Message-ID: <444F9DA7.2060402@domain.hid> (raw)
In-Reply-To: <444F9BDB.200@domain.hid>
Jan Kiszka wrote:
> adeos-cvs-request@domain.hid wrote:
>
>>...
>>Commit from rpm (2006-04-26 17:41 CEST)
>>---------------
>>
>>Make IPIPE_TRACE_PATHS configurable
>>
>> ipipe v2.6/common/kernel/ipipe/tracer.c 1.10
>> ipipe v2.6/common/kernel/ipipe/Kconfig.trace 1.4
>
>
> From a quick glance it appears to me you provided a nice interface to
> break some stuff :). At least the explanation is not correct.
>
> Those four paths are required to 1) always have an active path at hand
> for recording, 2+3) keep the latest max or frozen path, and 4) escape
> with to an alternative slot during max/frozen updates in case the
> previous one is currently locked for output or whatever and cannot
> become the new active path.
>
> So, the absolute minimum is 3 when there is definitely no concurrent
> usage of ipipe_trace_begin/end vs. ipipe_trace_freeze (remember that
> users may want to define their own begin/end points if
> IPIPE_TRACE_IRQSOFF is not set). Raising it above 4 is of no practical
> use so far.
>
> What is your idea behind it?
>
My idea is that 4 paths consume way too much memory and causes my
embedded ppc setup to choke at boot. The usual culprits like a bad
download address passed to u-boot and friends are not involved this
time, so until I figure out what on earth is causing this havoc, I'd
like to be able to lower this value to 2 by configuration.
--
Philippe.
next prev parent reply other threads:[~2006-04-26 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1FYmA5-0003S9-00@domain.hid>
2006-04-26 16:12 ` [Adeos-main] Re: Adeos-cvs Digest, Vol 10, Issue 11 Jan Kiszka
2006-04-26 16:19 ` Philippe Gerum [this message]
2006-04-26 16:26 ` Jan Kiszka
2006-04-26 16:40 ` Philippe Gerum
2006-04-26 16:30 ` Philippe Gerum
2006-04-26 16:20 ` Philippe Gerum
2006-04-26 16:28 ` Jan Kiszka
2006-04-26 16:38 ` 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=444F9DA7.2060402@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=jan.kiszka@domain.hid \
/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.