From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
Frede Florian <florian.frede@ma-info.de>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] i-Pipi patch 3.14
Date: Thu, 30 Oct 2014 14:41:14 +0100 [thread overview]
Message-ID: <54523FFA.8020707@siemens.com> (raw)
In-Reply-To: <20141030091631.GD11210@sisyphus.hd.free.fr>
On 2014-10-30 10:16, Gilles Chanteperdrix wrote:
> On Thu, Oct 30, 2014 at 10:06:44AM +0100, Frede Florian wrote:
>> Hello,
>>
>> I tried to patch the Kernel 3.14.22 and there is two new lines in
>> the file fs/exec.c
>>
>> tsk->mm->vmacache_seqnum = 0;
>> vmacache_flush(tsk);
>>
>> I am not sure if the line from the iPipe patch should placed before
>> or after this lines...
>>
>> + ipipe_mm_switch_unprotect(flags);
>
> We do not have enough information to understand what you
> are talking about. Show us the conflict as obtained with git merge
> or with patch --merge to give us more information.
I've resolved the conflict with the vma caching that was back-ported to
3.14.x in ipipe-jki.git [1] (for-upstream/3.14 branch). Kernel works
fine so far, but I didn't look into the details, if that caching thing
affects us in the RT domain as well and requires more work.
Jan
[1] http://git.xenomai.org/ipipe-jki.git
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-10-30 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 9:06 [Xenomai] i-Pipi patch 3.14 Frede Florian
2014-10-30 9:16 ` Gilles Chanteperdrix
2014-10-30 13:41 ` Jan Kiszka [this message]
2014-10-31 8:37 ` 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=54523FFA.8020707@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=florian.frede@ma-info.de \
--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.