From: Jan Kiszka <jan.kiszka@domain.hid>
To: Sebastian Smolorz <ssm@domain.hid>
Cc: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
adeos-main@gna.org
Subject: Re: [Adeos-main] [PATCH] I-pipe tracer for ARM
Date: Tue, 05 Dec 2006 17:48:00 +0100 [thread overview]
Message-ID: <4575A2C0.6000305@domain.hid> (raw)
In-Reply-To: <E1GrdKV-00048O-FF@mailer.emlix.com>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Sebastian Smolorz wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> Gilles Chanteperdrix wrote:
>>>> Jan Kiszka wrote:
>>>>> Sebastian Smolorz wrote:
>>>>>> Jan Kiszka wrote:
>>>>>>> Are you tracing into vmalloc'ed memory?
>>>>>> Yes, without CONFIG_IPIPE_TRACE_VMALLOC the system does not boot.
>>>>> Hmm, makes me wonder of some laziness of the page mapping or a missing
>>>>> lock-against-swapping causes this. Could you have a closer look at the
>>>>> tracer code if we are lacking some magic for the vmalloc trace buffer
>>>>> (compare to the xnheap code, e.g.)?
>>>> This is a known issue, the ARM architecture lacks the set_pgdir
>>>> function, needed in mm/vmalloc.c to workaround the lazy page mapping of
>>>> vmalloced areas.
>>> Would vmalloc+memset help to be safe for the remaining system runtime?
>> Probably not, the vmalloced area is added only to the page table of the
>> process that calls vmalloc, it is added to other processes table page
>> only once they use it.
>
> Are there any alternatives? Or do we have to live with this restriction?
>
Try if smaller CONFIG_IPIPE_TRACE_SHIFT makes it boot without
CONFIG_IPIPE_TRACE_VMALLOC.
On the longer term: Gilles, what does "lacks the set_pgdir" means? Is
this fixable?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-12-05 16:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 17:23 [Adeos-main] [PATCH] I-pipe tracer for ARM Sebastian Smolorz
2006-12-04 17:48 ` Jan Kiszka
2006-12-05 9:26 ` Sebastian Smolorz
2006-12-05 9:36 ` Jan Kiszka
2006-12-05 14:09 ` Sebastian Smolorz
2006-12-05 14:31 ` Jan Kiszka
2006-12-05 14:38 ` Gilles Chanteperdrix
2006-12-05 14:40 ` Jan Kiszka
2006-12-05 14:56 ` Gilles Chanteperdrix
2006-12-05 16:39 ` Sebastian Smolorz
2006-12-05 16:48 ` Jan Kiszka [this message]
2006-12-05 18:34 ` Sebastian Smolorz
2006-12-05 18:51 ` Jan Kiszka
2006-12-06 8:19 ` Sebastian Smolorz
2006-12-06 10:16 ` Jan Kiszka
2006-12-06 16:05 ` Sebastian Smolorz
2006-12-08 15:57 ` Jan Kiszka
2006-12-05 16:52 ` Gilles Chanteperdrix
2006-12-05 9:08 ` Gilles Chanteperdrix
2006-12-05 10:18 ` Sebastian Smolorz
2006-12-05 13:06 ` 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=4575A2C0.6000305@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=ssm@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.