From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: I-pipe 1.7 breaks mlockall safety check
Date: Thu, 15 Feb 2007 18:25:45 +0100 [thread overview]
Message-ID: <1171560346.24117.77.camel@domain.hid> (raw)
In-Reply-To: <45D46704.9050109@domain.hid>
On Thu, 2007-02-15 at 14:58 +0100, Jan Kiszka wrote:
> Philippe Gerum wrote:
> > On Thu, 2007-02-15 at 14:06 +0100, Jan Kiszka wrote:
> >> Hi all,
> >>
> >> I think I found another unwanted side-effect of the no-cow changes:
> >>
> >> With the I-pipe 1.7 patch series the test for missing mlockall no longer
> >> works. I just - once again - wrote a test program that was lacking this
> >> call, but only with I-pipe 1.6-06 (same Xenomai version: latest trunk) I
> >> get the usual error message on startup.
> >>
> >
> > I can't reproduce this with 1.7-01 here. Which Xenomai codebase are you
> > currently using (trunk/, 2.3.x maintenance or stock 2.3)?
>
> Specifically trunk, but the first observation was over 2.3.x
> maintenance. The test code is using the posix skin.
I still don't find any explanation for that behaviour, only trivially
testing with and without mlockall() in a bare main routine though.
In relation to this, I've rolled out 1.7-02/x86, so that we could close
the last pending issue(s) holding v2.3.1 wrt the interrupt pipeline
support. Specifically, the -nocow related changes have been amended, and
we are now back to the implementation that prevailed in the 1.6 series
wrt vmalloc and ioremap memory, while still retaining the ability to
break COW eagerly for the RT threads.
Feedback welcome on this.
--
Philippe.
next prev parent reply other threads:[~2007-02-15 17:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 13:06 [Xenomai-core] I-pipe 1.7 breaks mlockall safety check Jan Kiszka
2007-02-15 13:56 ` [Xenomai-core] " Philippe Gerum
2007-02-15 13:58 ` Jan Kiszka
2007-02-15 17:25 ` Philippe Gerum [this message]
2007-02-16 9:07 ` Jan Kiszka
2007-02-18 23:20 ` Jan Kiszka
2007-02-18 23:31 ` Gilles Chanteperdrix
2007-02-18 23:50 ` Philippe Gerum
2007-02-19 0:20 ` Gilles Chanteperdrix
2007-02-19 7:30 ` Jan Kiszka
2007-02-19 12:31 ` Jan Kiszka
2007-02-19 12:36 ` Philippe Gerum
2007-02-19 21:24 ` Gilles Chanteperdrix
2007-02-19 22:43 ` Philippe Gerum
2007-02-19 8:10 ` Philippe Gerum
2007-02-19 22:48 ` Gilles Chanteperdrix
2007-02-19 23:26 ` 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=1171560346.24117.77.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=jan.kiszka@domain.hid \
--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.