All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Richard Cochran <richard.cochran@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] FW: [PATCH] repost: ARM FCSE
Date: Sat, 27 Sep 2008 19:53:02 +0200	[thread overview]
Message-ID: <48DE72FE.4070809@domain.hid> (raw)
In-Reply-To: <48D9364B.70505@domain.hid>

Gilles Chanteperdrix wrote:
> Gilles Chanteperdrix wrote:
>> Richard Cochran wrote:
>>> I posted this patch today on linux-arm-kernel, but I repeat it
>>> here because there does not seem to be too much interest on that
>>> list for the ARM FCSE.
>>>
>>> I also tried to combine this patch with ipipe for kernel 2.6.20
>>> running on the Intel IXDP465, but after booting I soon get a BUG.
>>>
>>> Anyhow, perhaps the ARM people might take a look at combining
>>> ipipe with FCSE...
>> Ok. Six monthes later, I finally gave a try to your patch on at91rm9200,
>> which supports FCSE as well.
>>
>> When booting, I get random segmentation faults (either with or without
>> the I-pipe), assertion which fails in glibc, and such things.
> 
> A small update: I get the same random failures with a vanilla kernel
> (without I-pipe patch at all).
> 
> I will now investigate pmd_populate.

Hi Richard,

I changed a few bits here and there in your patch, but I believe the
biggest problem was that Linux seem to recycle pids faster than it
recycles mm_struct, so we ended up with processes sharing the same
space, and since the pid allocation mechanism was a bit too naive for
multi-threaded applications, I changed it to a bitfield based solution.
I now have an FCSE kernel which seems much more stable (and without the
double mapping either). This is the good news.

The bad news is that I still get mysterious crashes. So, will now
investigate.

Regards.

-- 
					    Gilles.


  parent reply	other threads:[~2008-09-27 17:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 16:19 [Adeos-main] FW: [PATCH] repost: ARM FCSE Richard Cochran
2008-03-07 16:31 ` Gilles Chanteperdrix
2008-09-21 15:52 ` Gilles Chanteperdrix
2008-09-21 16:30   ` Gilles Chanteperdrix
2008-09-23 18:32   ` Gilles Chanteperdrix
2008-09-24  5:47     ` Richard Cochran
2008-09-24  7:38       ` Gilles Chanteperdrix
2008-09-27 17:53     ` Gilles Chanteperdrix [this message]
2008-10-02  8:44       ` Gilles Chanteperdrix
2008-10-02 14:54         ` Richard Cochran
2008-10-02 15:30           ` Gilles Chanteperdrix
2008-10-02 17:36             ` Gilles Chanteperdrix
2008-10-02 20:03           ` Gilles Chanteperdrix
2008-10-03  7:20             ` Richard Cochran
2008-10-02 22:04         ` Bosko Radivojevic
2008-10-02 22:34           ` Gilles Chanteperdrix
2008-10-03  1:57             ` 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=48DE72FE.4070809@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=adeos-main@gna.org \
    --cc=richard.cochran@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.