From: Jan Kiszka <jan.kiszka@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>,
Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] pull request for the ipipe-3.10 branch
Date: Mon, 24 Feb 2014 16:49:13 +0100 [thread overview]
Message-ID: <530B69F9.3000501@siemens.com> (raw)
In-Reply-To: <530B608E.8070304@xenomai.org>
On 2014-02-24 16:09, Philippe Gerum wrote:
> On 02/24/2014 01:07 PM, Gilles Chanteperdrix wrote:
>> On 02/24/2014 09:56 AM, Jan Kiszka wrote:
>>> On 2014-02-24 01:29, Gilles Chanteperdrix wrote:
>>>> Hi,
>>>>
>>>> The following changes since commit
>>>> ce5bfa8a3282c8f97d5ec4b36802333b29e8c241:
>>>>
>>>> ipipe: fix wrong assumption in startup code of rt-timers (SMP)
>>>> (2014-02-13 15:22:15 +0100)
>>>>
>>>> are available in the git repository at:
>>>>
>>>> git://git.xenomai.org/ipipe-gch.git for-ipipe-3.10
>>>>
>>>> for you to fetch changes up to
>>>> da6384562ba94d28ffa7931e016a26b7db0b8ef5:
>>>>
>>>> ipipe/omap4: use the L2 cache write-allocate option (2014-02-24
>>>> 01:26:47 +0100)
>>>>
>>>> ----------------------------------------------------------------
>>>> Charles Steinkuehler (1):
>>>> arm/ipipe: fix compilation error with THUMB2
>>>>
>>>> Gilles Chanteperdrix (6):
>>>> arm/ipipe: fetch processor id from threadinfo in non-legacy mode
>>>> ipipe: introduce the ipipe_smp_p predicate
>>>> ipipe/spinlocks: use ipipe_smp_p to optimize-out spinlocks code
>>>> ipipe/arm: optimize the SMP_ON_UP case
>>>> ipipe/arm: add an option to disable L2 cache write-allocate
>>>> ipipe/omap4: use the L2 cache write-allocate option
>>>>
>>>> arch/arm/include/asm/barrier.h | 44
>>>> +++++++++++++++++++++++++------
>>>> arch/arm/include/asm/hardware/cache-l2x0.h | 2 ++
>>>> arch/arm/include/asm/ipipe.h | 6 +++++
>>>> arch/arm/include/asm/ipipe_base.h | 32
>>>> +++++++++++++++++++++-
>>>> arch/arm/include/asm/percpu.h | 4 +--
>>>> arch/arm/kernel/entry-armv.S | 2 ++
>>>> arch/arm/kernel/ipipe.c | 22 +++++++++++++++-
>>>> arch/arm/mach-omap2/omap4-common.c | 3 ++-
>>>> arch/arm/mm/cache-l2x0.c | 13 +++++++++
>>>> include/linux/ipipe.h | 6 +++++
>>>> kernel/ipipe/core.c | 20 ++++++++------
>>>> 11 files changed, 133 insertions(+), 21 deletions(-)
>>>>
>>>
>>> Could we do a stable update at this chance? There is a trivial conflict
>>> in generic code and one in ARM in order to use recent 3.10. Maybe you
>>> can have a look at the latter, Gilles:
>>>
>>> http://git.xenomai.org/ipipe-jki.git/commit/?h=for-upstream/3.10&id=63866844101456d3f2f2405620eee7c4ad0bd88d
>>>
>>
>> Since we are going to have to retest everything anyway when I am done
>> with the fd stuff, I would tend to prefer postponing the I-pipe stable
>> update at the same time. Even further than that: when we are ready to
>> release 3.0, so that if stable had a few more commits in the mean-time,
>> we will avoid useless tests.
>>
>
> Although time gets closer to the first 3.0-rc release, this is still a
> few months ahead, and we are already lagging significantly behind
> mainline wrt kernel updates.
>
> It looks like Jan's team is ok to validate 3.10-stable on x86, and I can
> do the same for other archs in the coming week. Let's roll out the
> patches for these archs, postponing arm until you get a chance to fixup
> the change impacting fcse there (does not seem bad at first glance).
Thanks!
>
> Next on my plate will be to move the generic pipeline core to 3.14,
> unless Jan has this brewing already.
Sorry, not this time. But, unless you are targeting x86 for the first
version, I will look into this afterward.
>
> Sorting out the issues which might remain regarding the RTDM API updates
> will go a long way toward getting 3.x out.
Yeah...
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-02-24 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 0:29 [Xenomai] pull request for the ipipe-3.10 branch Gilles Chanteperdrix
2014-02-24 8:56 ` Jan Kiszka
2014-02-24 9:41 ` Jan Kiszka
2014-02-24 12:07 ` Gilles Chanteperdrix
2014-02-24 12:54 ` Jan Kiszka
2014-02-24 15:09 ` Philippe Gerum
2014-02-24 15:49 ` Jan Kiszka [this message]
2014-02-24 17:51 ` 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=530B69F9.3000501@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=rpm@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.