Philippe Gerum wrote:
> 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.

From first tests it looks like the BUGs on RTnet startup are resolved
with 1.7-02. I will have a look at the mlockall issue again to
understand what happens precisely there (I'm still lacking the warning).


Attachment: signature.asc
Description: OpenPGP digital signature

Xenomai-core mailing list

Reply via email to