From: Jeff Weber <jweber@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai Help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] page faults
Date: Tue, 17 Apr 2007 08:21:10 -0500 [thread overview]
Message-ID: <200704170821.10282.jweber@domain.hid> (raw)
In-Reply-To: <17955.60369.329951.993803@domain.hid>
On Monday 16 April 2007 16:34, Gilles Chanteperdrix wrote:
> Jeff Weber wrote:
> > On Monday 16 April 2007 15:43, Gilles Chanteperdrix wrote:
> > > If the fault you observe is due to an access to some memory after a
> > > call to fork or one of its derivative (such as system, popen, etc...),
> > > the patch would have copied the whole real-time process address space
> > > at fork time instead of setting up COW mappings.
> >
> > No process forks are involved. Though mlockall() was called from Linux
> > main(), and the page fault was encountered by a separate Xenomai task.
> > Here's the task history:
>
> The fork may well be hidden in some library. The best way to know if
> there is really no fork is to register a callback with pthread_atfork.
pthread_atfork confirms that there is no fork.
Jeff
--
Jeff Weber
American Superconductor Corp.
next prev parent reply other threads:[~2007-04-17 13:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 19:49 [Xenomai-help] page faults Jeff Weber
2007-04-16 20:05 ` Philippe Gerum
2007-04-16 20:20 ` Jeff Weber
2007-04-16 20:43 ` Gilles Chanteperdrix
2007-04-16 21:27 ` Jeff Weber
2007-04-16 21:34 ` Gilles Chanteperdrix
2007-04-17 13:21 ` Jeff Weber [this message]
2007-04-17 19:17 ` Gilles Chanteperdrix
2007-04-17 20:59 ` Jeff Weber
2007-04-20 16:43 ` Jeff Weber
2007-04-20 17:24 ` Philippe Gerum
-- strict thread matches above, loose matches on Subject: below --
2006-02-28 14:22 [Xenomai-help] Page faults Jeroen Van den Keybus
2006-02-28 15:05 ` Jan Kiszka
2006-02-28 15:29 ` Jeroen Van den Keybus
2006-02-28 16:29 ` Jan Kiszka
2006-02-28 16:31 ` Philippe Gerum
2006-02-28 17:08 ` Jeroen Van den Keybus
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=200704170821.10282.jweber@domain.hid \
--to=jweber@domain.hid \
--cc=gilles.chanteperdrix@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.