From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>,
adeos-main <adeos-main@gna.org>, Philippe Gerum <rpm@xenomai.org>
Subject: Re: [Adeos-main] [PATCH] tracer: use per-cpu trace buffers
Date: Sat, 23 Feb 2008 13:35:12 +0100 [thread overview]
Message-ID: <47C01300.9070204@domain.hid> (raw)
In-Reply-To: <18367.7523.207507.331701@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
> > This patch addresses two issues:
> >
> > - fixes boot hang with CONFIG_IPIPE_TRACE, !CONFIG_IPIPE_TRACE_VMALLOC,
> > and large CONFIG_NR_CPUS (due to the huge trace buffers this implies,
> > even if the system has only a few CPUs in fact)
>
> This is something I observed even on UP systems: the kernel does not
> boot on ARM if CONFIG_IPIPE_TRACE_VMALLOC is not selected.
>
Yeah, well known, that's why we have vmalloc'ed trace buffers.
I just wondered again if this is an arch-specific issue, or if it
depends on the RAM size. If it is arch-specific, you are welcome to
change the default of IPIPE_TRACE_VMALLOC ("default y if ARM || ...").
Or reduce IPIPE_TRACE_SHIFT for ARM, given there is a reasonable value
(/wrt to the tracer) your boards still boot with.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2008-02-23 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 10:36 [Adeos-main] [PATCH] tracer: use per-cpu trace buffers Jan Kiszka
2008-02-22 19:07 ` Gilles Chanteperdrix
2008-02-23 12:35 ` Jan Kiszka [this message]
2008-02-23 13:05 ` Gilles Chanteperdrix
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=47C01300.9070204@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=rpm@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.